npm-check vs Rev-dep
npm-check reports unused dependencies and out-of-date packages, with an interactive updater. rev-dep replaces its unused-dependency analysis and adds far more - but it does not manage package versions.
At a glance
| npm-check | Rev-dep | |
|---|---|---|
| Primary focus | unused deps + version updates | dependency hygiene + architecture |
| Runtime | Node | Go - single parallel pass (faster) |
| Unused dependencies | yes | yes |
| Missing dependencies | not a focus | yes |
| Outdated / interactive update | yes | no |
| Unused exports / orphan files / cycles | no | yes |
| Maintained | effectively no (last release 2022) | yes |
Where rev-dep is stronger
- Maintained and fast.
- Broader - it also detects missing dependencies, dev-deps in production, unused exports, orphan files, and architecture rules.
Where npm-check may still fit
npm-check's interactive version updater (-u) is outside rev-dep's scope entirely. For checking and bumping outdated packages, keep npm outdated or npm-check-updates - rev-dep focuses on whether dependencies are used and declared, not their versions.
Which should you choose?
- Want an interactive "update my outdated packages" flow? npm-check (or npm-check-updates).
- Want maintained, fast unused/missing-dependency detection plus broader hygiene? rev-dep.