📦 npm Package Scraper — Metadata, Dependencies, Maintainers & Versions

Bulk-extract package metadata from the npm registry: name, description, latest version, full dependency tree, dist-tags, maintainers, repository link, license, weekly download stats, and version history. A pay-per-result alternative to libraries.io API, npms.io, Snyk Advisor, and OSS Insight — purpose-built for developer-tools founders sizing markets, supply-chain security teams auditing dependency surface, and DevRel teams tracking package adoption.

Why npm Package Scraper Beats libraries.io, npms.io, Snyk Advisor & OSS Insight

Feature	NexGenData npm Scraper	libraries.io API	npms.io	Snyk Advisor	OSS Insight
Cost	$2 per 1K packages, pay-per-event	Free (heavy throttle)	Free	$25-99 / dev / month	$$ / month
Dependency tree depth	Full (resolved)	One level	One level	Vuln-focused	Limited
Maintainer + repo metadata	Yes	Yes	Yes	Limited	Yes
Weekly downloads	Yes	No	Yes	No	Yes
Version history	Yes — all versions + dates	Yes	Yes	Limited	Limited
Bulk export	JSON / CSV / Excel	Plan-gated	Plan-gated	CSV	Plan-gated
Auth	Apify token	API key	None	Snyk account	OSS Insight account
Rate limit	None (Apify proxies)	Strict	Strict	Per-account	Per-account

Most teams pick this actor instead of maintaining a custom npm-registry harvester because it is the drop-in alternative to libraries.io that doesn't bonk you with rate limits on the first thousand packages — cheaper than Snyk Advisor for non-security audits, and drop-in compatible with downstream BI tools.

What You Get Per Package

Each dataset item is a flat record:

• name — package name
• description
• latest_version
• versions[] — every published version with {version, published_at}
• dependencies — production deps map
• dev_dependencies, peer_dependencies, optional_dependencies
• dist_tags — e.g. {latest, next, beta}
• maintainers[] — {name, email}
• repository — {type, url}
• homepage, license, keywords[]
• weekly_downloads, monthly_downloads
• created_at, modified_at
• unpacked_size, file_count — for latest tarball

Use Cases

• Developer-tools founders — map the addressable market for a new build tool by counting packages with relevant keywords
• Supply-chain security teams — audit the resolved dependency tree of a private monorepo against the live npm registry
• DevRel / open-source maintainers — track adoption of your library by measuring downstream-dependents growth week-over-week
• VC analysts — flag breakout dev-tool packages early by sorting on weekly_downloads velocity
• Engineering managers — generate package-health scorecards (last-modified, maintainer count, dependents) for internal tech-debt reviews

Quick Start

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("nexgendata/npm-scraper").call(run_input={
    "packages": ["react", "vue", "svelte", "next", "remix"]
})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["name"], item["latest_version"], item["weekly_downloads"])

Pricing

Pay-per-event:

• Actor Start: small fixed charge per run (memory-scaled)
• Per package: $2 per 1,000 packages returned

No subscription, no minimum.

Related NexGenData Actors

Use case	Actor
PyPI Python package scraper	pypi-scraper
npm package download statistics	npm-package-stats
PyPI package download statistics	pypi-package-stats
GitHub trending repositories	github-trending-repos
GitHub repository deep-stats	github-repo-stats
Stack Overflow Q&A scraper	stackoverflow-questions
Developer tools intelligence MCP	developer-tools-mcp-server
Hacker News scraper	hacker-news-scraper

FAQ

Does the actor resolve transitive dependencies? Yes — the dependencies field is the package's declared deps, and a resolved_dependencies array contains the fully resolved transitive graph (depth-capped at 5 for performance).

Do you cover unscoped and scoped packages? Yes — both react and @scope/package are supported.

How often is download data refreshed? Weekly download counts come from the npm public API, refreshed daily by npm itself.

Output formats? JSON, CSV, Excel, and the Apify dataset API.

Is this legal? Yes — npm registry data is public and intentionally exposed for tooling like this.

About NexGenData

NexGenData publishes 260+ buyer-intent actors covering SEC filings, YC alumni, lead generation, competitive intelligence, stock fundamentals across 30+ exchanges, and more. All pay-per-result. Browse the full catalog at https://apify.com/nexgendata?fpr=2ayu9b

---

How NexGenData Pricing Works

Every NexGenData actor uses pay-per-event pricing — you only pay for results that actually land in your dataset. No monthly minimum, no seat fees, no surprise overage bills.

• Actor Start: a single-event charge each time you spin the actor up (scaled to memory size)
• Result / item: charged per item written to the default dataset
• No charge for retries, internal proxy rotation, or failed sub-requests — those are absorbed by the platform

Apify Platform Bonus

New to Apify? Sign up with the NexGenData referral link — you get free platform credits on signup (enough for several thousand free results) and you help fund the maintenance of this actor fleet.

Integration Surface

Every actor in the NexGenData catalog can be triggered from:

• Apify console — point-and-click run
• Apify API — REST + webhooks
• Apify Python / JS SDKs — programmatic batch
• Zapier, Make.com, n8n — official integrations
• MCP — many actors are exposed as MCP tools for Claude / ChatGPT / Cursor agents
• Schedules — built-in cron for daily / weekly / monthly runs
• Webhooks — POST results to any HTTPS endpoint on dataset write

Support

NexGenData maintains 260+ Apify actors and ships updates regularly. Bug reports via the Apify console issues tab get a response within 24 hours. Roadmap requests are welcome — high-demand features ship in the next version.

Home: thenextgennexus.com Full catalog: apify.com/nexgendata