How much does Package Registry Scraper (npm + PyPI) cost?

$0.002 per package — $2 per 1,000. Billing is pay-per-result on your own Apify account: no subscription, and a run that returns nothing costs nothing.

What do I need to provide to run Package Registry Scraper (npm + PyPI)?

Nothing is mandatory — every field has a working default. The settings you will usually change are Registry, Search query (npm only), Package names (exact), Include monthly downloads (npm), Max packages (npm search).

Do I need to code to use Package Registry Scraper (npm + PyPI)?

No. It is a ready-to-run cloud tool: open it on Apify, fill in the form, click Run, and download the results. Everything runs on Apify's servers, so there is nothing to install or host.

Package Registry Scraper (npm + PyPI)

Q: What data does Package Registry Scraper (npm + PyPI) return?

A structured dataset with 12 fields per record, including author, description, homepage, keywords, license, monthlyDownloads, name, registry, repository, score, url, version. Export it as JSON, CSV or Excel, or send it straight to your app, a database or an AI agent.

Get npm and PyPI package metadata - version, license, repo, keywords, and npm download counts. Search by keyword or look up exact names. No API key needed.

5 from 1 review on Apify 158 runs on Apify $0.002 per package ($2 / 1,000)

Run this in the cloudRun on Apify →

Developer & Research Tools

How it works

1
Open it on Apify
Hit Run on Apify — it opens the tool in the cloud, no install.
2
Set the inputs
Adjust registry, searchQuery, packageNames (sensible defaults are pre-filled).
3
Click Run
The tool runs on Apify’s cloud and collects the data for you.
4
Export the results
Download as JSON, CSV or Excel, or pipe straight into your app, Google Sheets, or an AI agent.

Pricing

$0.002 per package = $2 per 1,000

You are charged for	When	Price
Package returned	Charged per package returned.	$0.002

Pay-per-event pricing: you are billed per result, not per subscription — a run that returns nothing costs nothing beyond the start fee. Billing is handled by Apify on your own account. These are the live Apify store prices, in effect since 2026-06-13, and they are what you are actually charged.

Inputs

Field	What it does	Type
`registry`	Which package registry to use. npm supports both keyword search and exact-name lookup; PyPI supports exact-name lookup only (it has no clean public search API).	string
`searchQuery`	Keywords to search the npm registry for (e.g. "react state management"). npm only — ignored for PyPI. Leave empty if you are looking up exact package names instead.	string
`packageNames`	Exact package names to look up directly. Works for BOTH registries. For PyPI this is the only supported mode (e.g. ["requests", "fastapi"]). For npm, scoped names like "@types/node" are supported.	array
`includeDownloads`	Fetch last-month download counts for each npm package via the npm downloads API. npm only — PyPI does not expose a public download-count endpoint. Adds one request per package. Note: monthlyDownloads is null when this is off, for PyPI packages, or if the downloads API call fails for a given package (a warning is logged in that case).	boolean
`maxItems`	Maximum number of packages to return from an npm search query. Only applies to npm search; ignored for exact-name lookups.	integer
`notionConnector`	Optional. Write each package as a page into your Notion when the run finishes. Authorize a Notion connector once in Settings → API & Integrations → MCP connectors, then pick it here. Leave empty to skip (default) — results are always saved to the dataset regardless.	string
`notionParentId`	Optional. The Notion data source ID of the database to write into (only used if a Notion connector is set). Leave empty to create the pages privately in your workspace instead.	string

What you get

A structured dataset — each result includes fields like:

authordescriptionhomepagekeywordslicensemonthlyDownloadsnameregistryrepositoryscoreurlversion

Export every run as JSON, CSV or Excel, or send it to your app, a database, Google Sheets, or an AI agent.

2 ready-to-run use cases

npm Search Scraper: Downloads, License & Repo

Search the npm registry by keyword and compare each package's version, license, source repo, and monthly downloads side by side. Great for JS library research.

npm License Audit: Map package.json Deps

Feed your package.json dependencies and return the license and source repository for each npm package - a fast OSS compliance check for engineering teams.

Related tools in Developer & Research Tools

Other ready-to-run tools in the same category — all pay-per-use on the Apify cloud.

Developer & Research Tools

arXiv Scraper

Search arXiv and get clean JSON: titles, abstracts, authors, categories, DOI, dates and PDF links. No API key. Sort by relevance or date; push to Notion.

2 use cases

Developer & Research Tools

OpenAlex Scholarly Works Scraper

Search 250M+ OpenAlex papers by keyword. Get titles, authors, venue, year, citations, concepts, OA links and full abstracts as structured JSON. No API key.

2 use cases

Developer & Research Tools

Crossref Scholarly Works Scraper

Search 150M+ scholarly works on Crossref and export DOI, authors, journal, citation count, and abstracts as JSON or CSV. Filter by type and date.

2 use cases

Developer & Research Tools

Wikipedia Scraper

Search Wikipedia by keyword or fetch clean page data (plain text, thumbnail, categories, URL) by title. No API key, no anti-bot. Up to 50 titles per batch.

3 use cases

Developer & Research Tools

Internet Archive Scraper

Search archive.org by keyword and export clean items (title, creator, year, downloads, item URL). Filter by media type, sort by popularity or date.

2 use cases

Developer & Research Tools

Hacker News Scraper

Search Hacker News stories, Show HN, Ask HN, comments, or the front page by keyword and get clean JSON with points, author and comment links.

3 use cases

See all Developer & Research Tools →

Where this tool sits

Categories: Developer & Research Tools
Platforms: Academic & Research

Package Registry Scraper (npm + PyPI)

Pull clean, structured package metadata from the npm and PyPI public registries. No API key, no login, no anti-bot. Search npm by keyword, or look up exact packages by name on either registry — and get a single normalized shape back for both.

$2.00 per 1,000 packages ($0.002 each), with no run-start fee. Flat rate — no volume tiers, no plan gates — and you are charged only for packages actually returned.

What you get per package

registry, name, version, description, author, homepage, repository (decoded to a browseable https URL), license, keywords, monthlyDownloads (npm), and url (the human-facing registry page).

Nullable fields. Registries don't always populate every field, so the following can be null: description, author, homepage, repository, license (and keywords may be an empty array). monthlyDownloads is null when includeDownloads is off, for PyPI packages (no public download endpoint), or if the npm downloads API call fails for a specific package — in which case a warning is logged so you know why.

Input

Field	Notes
`registry`	`npm` or `pypi`. Default `npm`.
`searchQuery`	Keyword search — npm only (PyPI has no clean public search API).
`packageNames`	Array of exact names — works for both registries (e.g. `["requests","fastapi"]`, or npm scoped `["@types/node"]`).
`includeDownloads`	Fetch last-month download counts for npm packages. On by default. npm only.
`maxItems`	Cap on npm search results. Default 50.

You must provide either a searchQuery (npm) or one or more packageNames.

Registries

npm — keyword search via the registry search API, package detail via registry.npmjs.org/{pkg}, and monthly downloads via api.npmjs.org.
PyPI — exact-name lookup via pypi.org/pypi/{pkg}/json. PyPI has no clean public search API, so a searchQuery with registry=pypi returns a single diagnostic row telling you to use packageNames instead.

Output

One dataset row per package, deduped by registry + name. Packages that can't be found, and empty searches, return a single diagnostic row (ok:false) and are not charged.

Pricing

Event	When	Price
Package returned	Each package row written to the dataset	$0.002 ($2.00 / 1,000)

No run-start fee — a run that returns nothing costs $0.00. Diagnostic rows (ok:false) — bad input, not-found packages, empty searches, network/registry errors — are never charged. A default 50-result npm search costs $0.10; looking up two exact packages costs $0.004.

monthlyDownloads is included at no extra charge: there is no separate "enrichment" event for it.

Proxy

These are public, no-auth registries with no anti-bot, so no proxy is needed — leave proxy off (the default). Only enable a proxy if you hit IP-based rate limits on very large runs.

Troubleshooting

Empty/bad-input run returns a BAD_INPUT diagnostic row: provide a searchQuery (npm) or one or more packageNames.
monthlyDownloads is null for some npm packages: the downloads API occasionally rate-limits or has no data for a package; the run logs a warning and continues with null for that field.
PyPI search isn't supported (PyPI has no clean public search API); use exact packageNames with registry=pypi.

Examples

Search npm:

{ "registry": "npm", "searchQuery": "react state management", "maxItems": 25, "includeDownloads": true }

Look up Python packages:

{ "registry": "pypi", "packageNames": ["requests", "fastapi"] }