Package Registry Monitor - npm, PyPI, crates.io
Pricing
from $5.00 / 1,000 packages
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
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
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:
| Field | Description |
|---|---|
name / registry | Package name and which registry it came from |
latestVersion | Current published version |
releasedAt | When that version shipped |
firstReleasedAt | When the package first appeared |
daysSinceRelease | Days since the newest release |
isStale | True if it has not shipped inside your threshold |
license | Declared licence |
repository / homepage | Normalised source and project links |
maintainers / maintainerCount | Who publishes it — bus-factor signal |
dependencies | Direct dependency count |
versionCount | Total released versions |
deprecated | Registry-flagged deprecation |
keywords | Declared keywords |
versionHistory | Last 10 releases with dates (optional) |
downloads | Total and recent downloads (crates.io) |
Input
{"packages": ["npm:react", "pypi:requests", "crates:serde"],"includeVersionHistory": true,"staleAfterDays": 365}
| Option | Default | What it does |
|---|---|---|
packages | required | registry:name. Aliases accepted: node→npm, pip/python→pypi, rust→crates |
includeVersionHistory | true | Attach the last 10 releases with dates |
staleAfterDays | 365 | Days 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,maintainerCountanddeprecatedtogether 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
dependenciescounts direct dependencies only, not the full transitive tree.- crates.io does not expose maintainers through this endpoint, so
maintainersis 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.