dep-pulse

See which of your dependencies are unmaintained, deprecated, or have better alternatives.

Install

npx dep-pulse

Or install globally:

npm install -g dep-pulse

Usage

dep-pulse

Run it in any project with a package.json:

Checking dependencies in /path/to/package.json...

Package │ Current │ Latest │ Published │ Downloads │ Status          │ Notes
──────────────────────────────────────────────────────────────────────────────────
express │ 4.18.2  │ 4.21.0 │ 3mo ago   │    32.1M  │ 🟢 healthy      │
request │ 2.88.2  │ 2.88.2 │ 5y ago    │     4.2M  │ 🔴 unmaintained │ deprecated
chalk   │ 4.1.2   │ 5.4.1  │ 8mo ago   │    98.7M  │ 🟢 healthy      │
moment  │ 2.30.1  │ 2.30.1 │ 2y ago    │    14.5M  │ 🟡 stale        │

  3 healthy, 1 stale, 1 unmaintained — 5 packages total

What it checks

• Last npm publish — when was the package last released?
• GitHub activity — recent commits, or has development stopped?
• Deprecation notices — flagged deprecated on npm
• Download trends — weekly download counts
• Archived repos — is the GitHub repo archived?

Status indicators

| Icon | Status | Meaning | |------|--------|---------| | 🟢 | healthy | Published within the last year, active development | | 🟡 | stale | No publish in over a year, but not dead | | 🔴 | unmaintained | Deprecated, archived, or no activity in 2+ years |

Options

Zero config. Just run dep-pulse in your project directory.

Pass a path to check a different project:

dep-pulse ./path/to/project

GitHub token

Set GITHUB_TOKEN to avoid GitHub API rate limits:

export GITHUB_TOKEN=ghp_xxxxx
dep-pulse

Without a token, GitHub checks may be rate-limited for large projects.

Why

npm outdated tells you version numbers. dep-pulse tells you if your dependencies are alive.

Version bumps don't matter if the maintainer disappeared two years ago. This tool gives you the health check that npm outdated never did.

License

MIT © pigeonflowai