npm Registry Scraper: Package Metadata & Releases
Pricing
Pay per usage
npm Registry Scraper: Package Metadata & Releases
Pull package metadata from the public npm registry: latest version, license, maintainers, dependency counts, release cadence and tarball size. No login, no proxy, no browser.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Naimur Hasan
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
9 days ago
Last modified
Categories
Share
npm Registry Scraper
Pulls package metadata from the public npm registry. No login, no proxy, no browser.
Input
| Field | Type | Notes |
|---|---|---|
packages | array | Required. One package name per line; scoped names are fine. |
mode | string | package (one row each) or releases (one row per version). Default package. |
maxReleases | integer | Release mode only, newest first. Default 50. |
Output
Package mode — name, description, latestVersion, license,
versionCount, distTags, created, lastPublished, latestPublished,
dependencyCount, dependencies, peerDependencyCount, maintainerCount,
keywords, homepage, repository, unpackedSizeBytes, fileCount,
tarball, deprecated, npmUrl.
Release mode — name, version, published, isLatest, deprecated,
unpackedSizeBytes, dependencyCount.
Notes
- A scoped name needs its slash percent-encoded.
@babel/corehas to be requested as@babel%2fcore; sent raw, the registry reads it as a path and 404s. timeis not purely a version map. It also holdscreatedandmodified, which are timestamps rather than versions and become phantom releases if iterated blindly.- Dependencies live on the per-version manifest, not the package document, so
they are read from
versions[latest]rather than the root. licensehas been a string, an object and an array across npm's history; all three spellings are handled.- A deprecated package still resolves normally — the deprecation notice is a field on the version, so it is surfaced rather than inferred.
