npm Package Health Checker — Spot Deprecated & Abandoned Dependencies
Paste your package.json — checks each dependency against the npm registry for deprecated status, last publish date, maintainer count, and download trends. Spot the packages worth replacing before they cause problems.
Paste your package.json (or just the dependencies object). Checks each package against the npm registry for deprecated status, last publish date, maintainer count, and weekly download trends — the signals that tell you whether a package is worth keeping.
What this checks (and why it matters)
- Deprecated packages: The author has marked it as deprecated and often suggests a replacement. Examples:
request→ usegotoraxios,node-uuid→ useuuid. - Abandoned packages: No publish in 2+ years. May still work, but security patches and Node.js compatibility updates stop.
- Single-maintainer packages: High bus factor. If the maintainer loses interest, the package gets abandoned. Worth checking for core dependencies.
- Weekly downloads: A proxy for community health. 100K+ downloads/week = actively used and maintained. Under 1K = niche or declining.
This complements the Vulnerability Scanner (which checks for CVEs). Use both: CVE scanner catches known exploits, this tool catches the “quietly falling apart” problem.
Founded
2023 in London, UK
Contact
hello@releaserun.com