Package Registry Monitor - npm, PyPI, crates.io avatar

Package Registry Monitor - npm, PyPI, crates.io

Pricing

from $5.00 / 1,000 packages

Go to Apify Store
Package Registry Monitor - npm, PyPI, crates.io

Package Registry Monitor - npm, PyPI, crates.io

Input: packages as npm:react, pypi:requests or crates:serde. Output: latest version, release date, licence, maintainers, dependency count and an abandonment flag. Use when you need to check whether a dependency is current, maintained or stale.

Pricing

from $5.00 / 1,000 packages

Rating

0.0

(0)

Developer

Alexandre de La Fayette

Alexandre de La Fayette

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Package Registry Monitor

Track open-source packages across npm, PyPI and crates.io with one schema and one run.

Reads each registry's official public JSON API — documented, unauthenticated endpoints built for exactly this. No scraping, no API keys, no rate-limit games.

What you get

One row per package:

FieldDescription
name / registryPackage name and which registry it came from
latestVersionCurrent published version
releasedAtWhen that version shipped
firstReleasedAtWhen the package first appeared
daysSinceReleaseDays since the newest release
isStaleTrue if it has not shipped inside your threshold
licenseDeclared licence
repository / homepageNormalised source and project links
maintainers / maintainerCountWho publishes it — bus-factor signal
dependenciesDirect dependency count
versionCountTotal released versions
deprecatedRegistry-flagged deprecation
keywordsDeclared keywords
versionHistoryLast 10 releases with dates (optional)
downloadsTotal and recent downloads (crates.io)

Input

{
"packages": ["npm:react", "pypi:requests", "crates:serde"],
"includeVersionHistory": true,
"staleAfterDays": 365
}
OptionDefaultWhat it does
packagesrequiredregistry:name. Aliases accepted: node→npm, pip/python→pypi, rust→crates
includeVersionHistorytrueAttach the last 10 releases with dates
staleAfterDays365Days before a package is flagged stale

Scoped npm packages work as-is: npm:@types/node.

Who this is for

  • Security and platform teams auditing dependencies for abandonment. isStale, maintainerCount and deprecated together are a decent bus-factor signal.
  • Engineering managers tracking whether critical dependencies are still maintained.
  • Investors and analysts measuring release cadence across an ecosystem.
  • Developer-tool companies monitoring competitor packages.
  • Anyone who wants npm, PyPI and crates.io in one schema instead of three APIs.

Honest limits

  • dependencies counts direct dependencies only, not the full transitive tree.
  • crates.io does not expose maintainers through this endpoint, so maintainers is empty there.
  • PyPI licence data is inconsistent across packages — it falls back to classifiers, but some projects declare neither.
  • Download counts are only available from crates.io. npm and PyPI serve those from separate endpoints not included here.

Pricing

Pay per event. Charged per package successfully resolved. A failed lookup costs nothing.

Changelog

1.0 — First release. npm, PyPI and crates.io with staleness detection.