npm Package Dependency Snapshot
Pricing
from $250.00 / 1,000 repo scans
npm Package Dependency Snapshot
Dependency names from registry.npmjs.org/apify/latest. Not a CVE audit. $0.002 / package.
Pricing
from $250.00 / 1,000 repo scans
Rating
0.0
(0)
Developer
Zentra
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Categories
Share
apify@latest dependency names from the npm registry. That is a lockfile-style list, not a vuln scanner.
Dependency names from registry.npmjs.org/apify/latest. Not a CVE audit. $0.002 / package.
Last run
Live row(s). First row: apify@3.7.2
{"title": "apify@3.7.2","entityName": "apify","listingName": "apify@3.7.2","productName": "apify@3.7.2","sourceUrl": "https://www.npmjs.com/package/apify","sourceName": "npm registry latest apify — dependency names, not a CVE audit"}
Run it
{"searchKeywords": ["apify"],"sourceMode": "startUrls","outputMode": "buyer-ready-records","maxItems": 10,"startUrls": [{"url": "https://registry.npmjs.org/apify/latest"}]}
What lands in the dataset
- registry.npmjs.org/apify/latest
- package version + dependency names
- npm URLs
Use it when
Point at another package in production. Try is apify.
Builders inventorying what an npm package pulls in.
Price
$0.002 / package — about $0.02 for a 10-row Try.
Schedule it. A one-off click is not Store revenue.
What you should know
- Not a CVE / advisory audit.
- Not SBOM attestation.
FAQ
Is the last-run a fixture? No. If the dataset is empty, the public source failed — we do not invent a row.
Does it flag CVEs? No. Dependency names only. Cross-check osv.dev yourself.