npm Package Dependency Intelligence
Pricing
Pay per usage
npm Package Dependency Intelligence
Analyze npm package metadata, versions, dependencies, maintainer hints, release cadence, and package risk signals using the official npm registry API.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
太郎 山田
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Analyze npm packages from the official registry.npmjs.org packument endpoint and export flattened rows for package summaries, version metadata, dependency declarations, maintainer hints, release cadence, and package hygiene signals.
This actor is built for direct package watchlists. It does not scrape npmjs.com HTML pages.
Inputs
| Field | Default | Notes |
|---|---|---|
packages | required | npm package names such as react, vite, express, or @types/node. |
includeVersionHistory | true | Emit package_version rows. When false, only the latest version row is emitted. |
includeDevDependencies | true | Include devDependencies from emitted versions. |
maxVersionRowsPerPackage | 100 | Cap version rows per package. |
maxDependencyRowsPerPackage | 250 | Cap dependency rows per package across emitted versions. |
concurrency | 5 | Parallel package fetches. |
timeoutMs | 15000 | Per-request timeout in ms. |
delivery | dataset | dataset or webhook. |
webhookUrl | empty | Required when delivery=webhook. |
dryRun | false | Skip dataset and webhook delivery. |
Dataset Rows
The dataset is flattened so it can be filtered and joined without unpacking one large object.
package_summary
packageName,normalizedPackageName,requestedName,statuslatestVersion,description,license,homepage,repositoryUrl,bugsUrlkeywords,author,maintainers,publisher,distTagsversionCount,emittedVersionCount,firstPublishedAt,latestPublishedAt,modifiedAtreleaseCadenceDays,dependencyCount,emittedDependencyCountnodeEngine,deprecated,warnings,fetchedAt
package_version
packageName,version,publishedAt,distTags,isLatestlicense,nodeEngine,deprecated- dependency group counts
tarballUrl,shasum,integrity,unpackedSize,fetchedAt
dependency
packageName,packageVersiondependencyName,normalizedDependencyNamedependencyGroupsuch asruntime,development,peer,optional, orbundledversionSpec,rawSpec,optional,bundled,fetchedAt
Example Input
{"packages": ["react", "vite", "@types/node"],"includeVersionHistory": true,"includeDevDependencies": true,"maxVersionRowsPerPackage": 25,"maxDependencyRowsPerPackage": 250,"concurrency": 3,"timeoutMs": 15000,"delivery": "dataset","webhookUrl": "","dryRun": false}
Local Development
npm installnpm testnode src/index.js
output/result.json contains the full payload for local inspection. On Apify, dataset delivery writes the flattened rows.
Limitations
- V1 is direct package lookup only; npm search and npmjs.com HTML pages are out of scope.
- Dependency declarations come from published package metadata in
registry.npmjs.org/{package}. - Historical dependency rows are capped by
maxVersionRowsPerPackageandmaxDependencyRowsPerPackage.