npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@stealth-alpha/repo-pulse

v0.1.0

Published

One-command repository health snapshot: commit velocity, bus factor, stale dependencies and issue half-life — emits badge-ready JSON + SVG.

Readme

repo-pulse

One command. One honest snapshot of your repository's health.

Every maintainer knows the questions that matter but are annoying to answer:

  • Is this repo still moving? — commit velocity over a trailing window
  • What happens if the main contributor disappears? — bus factor
  • Which of my dependencies rotted while I wasn't looking? — stale deps
  • Do issues actually get resolved here? — issue half-life

repo-pulse answers all four in one run and emits badge-ready JSON + SVG, so your README can show the truth without you maintaining a single badge by hand. Zero dependencies, Node 18+, runs entirely on your machine.

Install

npm install -g @stealth-alpha/repo-pulse

or run it once without installing:

npx @stealth-alpha/repo-pulse@latest

30-second quickstart

cd your-project

repo-pulse                 # human-readable snapshot in your terminal
repo-pulse --format json   # same data, machine-readable
repo-pulse badge           # writes .repo-pulse/*.svg + *.json badges

Sample output:

repo-pulse — repository health snapshot
repository: your-project (main)
head: 6946f23 @ 2026-08-21T22:58:08Z

commit velocity : 7.3/week avg over 12w (trend up, last 9, prev 5)
bus factor      : 2 (low) across 6 contributors — top: Ada (38%), Bob (24%), …
stale deps      : 1/14 older than 12m
  • [email protected] — last publish 2016-05-25 (3740d ago)
issue half-life : 4.5 days median time-to-close (3 open / 41 closed)

score           : 78/100 (grade B) [velocity 100, bus 50, deps 93, issues 97]

Drop the badges into your README like any other image:

![health](./.repo-pulse/health.svg)
![bus factor](./.repo-pulse/bus-factor.svg)

What each metric means

| Metric | Definition | | --- | --- | | Commit velocity | Average commits per week across the trailing window (default 12 weeks), plus an up/down/flat trend comparing the recent half to the older half. Merge commits excluded. | | Bus factor | Smallest number of contributors whose commit share covers ≥50% of history. 1 = critical, 2 = low, 3+ = healthy. | | Stale deps | Runtime + dev dependencies whose package's most recent npm publish is older than the threshold (default 12 months). Requires network; skipped gracefully offline. | | Issue half-life | Median time-to-close of recent GitHub issues (PRs excluded). Open issues are counted but don't affect the median. |

The overall score is a plain average of the available component scores — no magic weights, nothing hidden. When a metric can't be computed (offline, private issues), it's excluded from the average instead of silently guessed.

Configuration

Optional repo-pulse.config.json in your repository root:

{
  "weeks": 12,
  "maxAgeMonths": 12,
  "issues": {
    "enabled": true,
    "repo": "owner/name",
    "limit": 200
  },
  "badges": {
    "dir": ".repo-pulse"
  }
}

Run repo-pulse init to generate it. Every field has a CLI flag equivalent: --weeks, --stale-months, --repo, --out, --format, --write, --offline.

Badge formats

Each badge ships twice:

  • SVG (health.svg) — flat shields-style vector, self-contained, no CDN.
  • JSON (health.json) — shields.io endpoint format, so you can serve it yourself and consume it with shields' endpoint badge.

Privacy & network behavior

  • Git metrics never leave your machine.
  • Staleness checks hit registry.npmjs.org; issue metrics hit api.github.com (unauthenticated, public repos only).
  • Use --offline for strictly local operation; unavailable metrics are marked as such rather than faked.

License

MIT. See LICENSE.

Repo Pulse Pro

Shipping this across a portfolio of repositories? Repo Pulse Pro ($9/month) adds multi-repo batch snapshots with a single aggregated dashboard file, scheduled CI regeneration so your badges never go stale, trend history so you can see whether health is improving or drifting month over month, custom scoring profiles tuned to your team's definition of "healthy", and priority support. It's the same engine under the hood — Pro just stops you from running it by hand twenty times. License via Gumroad — link placeholder.