Package Registry Scraper - PyPI and npm metadata
Pricing
from $2.00 / 1,000 package rows
Package Registry Scraper - PyPI and npm metadata
Pull package metadata and full version history from PyPI and npm. Licences, versions, release dates, dependencies and vulnerability flags. No API keys, no browser.
Pricing
from $2.00 / 1,000 package rows
Rating
0.0
(0)
Developer
ttgi
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
19 days ago
Last modified
Categories
Share
Package Registry Scraper
Package metadata and full version history from PyPI and npm. No API keys, no browser.
What you get
For each package: latest version, summary, description, author, licence,
home page, docs URL, keywords, requires_python, classifiers, release count,
first and last release dates, created/modified timestamps, and — for PyPI —
known vulnerability flags.
Scoped npm packages work (@scope/name).
Usage
One package is one HTTP request, so a 50-package audit costs 50 requests.
Use cases
- Dependency audit — licence compatibility across a manifest
- Supply-chain triage — release cadence, first/last publish dates, sudden version jumps
- Vulnerability screening — PyPI advisory counts per package
- Version-history analysis — how long a package has been maintained
- Forensics — when did this dependency first appear, and how often has it shipped since?
Honest notes
registry: "both"queries PyPI and npm for each name. A name that exists on only one registry yields one row plus anot foundentry inerrors— that is expected, not a failure.- A npm package named the same as a PyPI one is a different package. This
scraper returns both, tagged by
registry, rather than guessing which you meant. vulnerabilityCountis populated from PyPI only; npm does not expose equivalent data here.yankedis true when a release was withdrawn upstream.
Pronouns: they/them.
