npm Package Health Auditor avatar

npm Package Health Auditor

Pricing

from $5.00 / 1,000 package audits

Go to Apify Store
npm Package Health Auditor

npm Package Health Auditor

Audit npm package maintenance, popularity, licensing, typings, deprecation, and metadata without an API key.

Pricing

from $5.00 / 1,000 package audits

Rating

0.0

(0)

Developer

Through My Own

Through My Own

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Audit public npm packages for maintenance, adoption, deprecation, licensing, typings, provenance metadata, and dependency footprint. The Actor uses the public npm registry and npm downloads API, so it needs no API key, browser, proxy, or customer account.

Use cases

  • Screen dependencies before adding them to an application.
  • Review stale or deprecated packages during upgrades.
  • Enrich software inventories with current npm metadata.
  • Schedule lightweight package-health checks for automation and AI agents.

Input

Provide 1–50 package names or npmjs.com package URLs.

{ "packages": ["apify", "typescript", "@types/node"] }

Output

One dataset row per package found, including latest version and publish date, weekly downloads, health score, deprecation status, license, typings, maintainers, dependency counts, recommendations, and the npm URL. Missing packages and failed requests are written to ERRORS and are not charged as package audits.

Pricing

Pay per event: a small Actor-start event plus $0.005 for each package successfully fetched and audited. Platform usage is included in the event price.

Limits and privacy

Results reflect public registry metadata at run time and are heuristic, not a security guarantee. The Actor never installs or executes packages. Input is sent only to fixed npm-owned API hosts. No credentials or personal data are required.

API and integrations

Run from Apify Console, API, schedules, webhooks, Make, Zapier, n8n, or an AI agent. Results are available as JSON, CSV, Excel, XML, RSS, or JSONL through the default dataset.

Changelog

  • 0.1.0: Initial production release.