How to Check npm Package Downloads, Health & Risk
Before you add (or keep) a dependency, you want to know if it is actually maintained and widely used. This pulls download trends, version history, maintainers and health signals straight from the npm registry for a list of packages, so you can audit dependencies or compare alternatives at a glance.
Steps
- List the packages. Add the npm package names you want to analyze — a single package or your whole dependency list.
- Run it. Run the npm Package Intelligence actor. It queries the official npm registry and download APIs.
- Read the health signals. See weekly/monthly downloads, latest version and release cadence, maintainer count and last-publish date — the markers of an active vs abandoned package.
- Export or compare. Export to JSON/CSV or pull via API to flag stale dependencies or compare competing packages side by side.
Frequently asked questions
How do I spot an abandoned package?
Look for a stale last-publish date, falling downloads and a single maintainer — all surfaced in one row per package.
Do I need an npm token?
No — it uses the public npm registry and download APIs, no key required.
Can I analyze my whole package.json?
Yes — paste the full dependency list and get one health row per package.
Try it now
Run it on Apify — no install, results in minutes.
Open on Apify