Open-source package health: activity, abandonment, deprecation, license class, dependency weight and build provenance.
payments ON MAINNET (real money) · 8 live endpoints
| Endpoint | Price | What it answers |
|---|---|---|
GET /npm-downloads | $0.02 | npm package adoption: downloads last week and month, plus trend within the month and a popularity band. |
GET /package-deps | $0.02 | Dependency weight of a package version: direct and transitive dependency counts and a light/moderate/heavy verdict. |
GET /package-health | $0.03 | Package health for npm, PyPI, Go, Maven, Cargo or NuGet: maintained, stale or abandoned, deprecation, license, adoption. |
GET /package-license | $0.02 | License of a package version classed as permissive, weak, strong or network copyleft, with commercial-use notes. |
GET /package-provenance | $0.02 | Does a package version carry build provenance (SLSA/sigstore attestations)? Signals a verifiable build, not safety. |
GET /package-versions | $0.02 | Recent versions of a package with publish dates, deprecation flags and release cadence in days between releases. |
GET /pypi-package | $0.02 | PyPI project facts: latest version, Python requirement, license, release freshness and whether the latest is yanked. |
GET /pypi-yanked | $0.02 | Was a PyPI release yanked? Exact version check with the maintainer's reason, upload date and file count. |
GET /catalog returns this list as JSON. Activity hub · uptime.
Package metadata computed from deps.dev (Google), the npm downloads API and the PyPI JSON API, provided as is. Activity and license signals are heuristics from public metadata, not legal advice, a license review or a security audit. License classes are simplified; read the actual license text before relying on it. Every paid response carries a disclaimer field.