npm Package Scraper — Downloads, Maintainers & Metadata avatar

npm Package Scraper — Downloads, Maintainers & Metadata

Pricing

from $2.30 / 1,000 results

Go to Apify Store
npm Package Scraper — Downloads, Maintainers & Metadata

npm Package Scraper — Downloads, Maintainers & Metadata

Scrape npm packages: name, version, description, keywords, license, repository, homepage, dependencies, version count, created/updated dates, monthly downloads, quality/popularity scores and maintainers with emails. Search by keyword or pass package names. For dev market research and lead gen.

Pricing

from $2.30 / 1,000 results

Rating

0.0

(0)

Developer

Haketa

Haketa

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 days ago

Last modified

Features

Limited permissions

Share

npm Package Scraper — Downloads, Maintainers, Scores & Metadata

The ultimate npm scraper for extracting package metadata, monthly download metrics, official npm quality/popularity/maintenance scores, dependency trees, and maintainer emails — without an npm account, API keys, or rate-limit hurdles. Search the entire npm ecosystem by keyword or direct package list and extract structured records ready for market analysis, developer recruiting, and supply-chain audits.

npm Registry Downloads + Maintainers Dev Market Intel Export Formats Deep Pagination


⚡ At a glance

FeatureSpecification
Data Targetnpm registry & download metrics database
Input OptionsSearch keywords, qualifiers (author:, keywords:), or direct package names
Output FormatsJSON, CSV, Excel, XML, HTML, API endpoint
Maintainer LeadsDirect maintainer names & verified contact emails (maintainerEmails)
Popularity SignalsDownload counts (day, week, month) + npm popularity/quality/maintenance scores
Dependency AuditingDirect runtime dependencies count + devDependencies count + unpacked install size
Pagination CapabilityUnlocked 1,000+ deep pagination (250 packages per batch, 0 = unlimited)
Proxy SupportFully compatible with Apify Datacenter proxies (default)
Average Run Speed~100 enriched packages in under 45 seconds

🔎 Why scrape npm packages?

npm is the single largest software registry in the world, powering the entire JavaScript and TypeScript ecosystem with over three million published modules. Every public package carries vital commercial and technical telemetry: who builds and maintains it, how many production systems install it every month, its dependencies, open-source licensing, tarball size, and npm's algorithmic health scores.

Gathering this information manually is impractical. Navigating thousands of package pages, inspecting JSON manifests, cross-referencing download charts, and digging out maintainer email addresses takes dozens of hours. This npm package scraper turns that manual task into a rapid, automated pipeline.

High-impact applications

  • Ecosystem & market intelligence — Track adoption patterns across frameworks, libraries, build tools, and developer utilities. Rank competitors by monthly downloads.
  • Developer lead generation & recruiting — Identify maintainers and open-source contributors with active email addresses for hiring, technical sales, dev marketing, or sponsorship.
  • Dependency & supply-chain security — Audit your organization's entire dependency tree, monitoring install sizes, release timestamps, and unmaintained licenses.
  • Competitive benchmark tracking — Monitor rival open-source packages over time, recording download spikes, version releases, and maintenance health scores.
  • Investment & tech trend signals — Quantify open-source developer velocity to detect emerging startups, frameworks, and developer tool markets.
  • Vulnerability mitigation & license compliance — Quickly isolate packages under restrictive or copyleft licenses (GPL, AGPL) across internal project requirements.
  • Developer developer-relations (DevRel) discovery — Discover prominent community creators and prolific maintainers to sponsor or invite to tech conferences.

🔍 Advanced Search Qualifiers Guide

The npm registry search endpoint supports powerful native search qualifiers that you can pass directly into searchTerms. Combine these to construct surgical queries:

QualifierExampleResult
author:<username>author:sindresorhusMatches packages authored by a specific user
maintainer:<username>maintainer:addyosmaniFinds packages where the specified user is a maintainer
keywords:<tag>keywords:cliFilters packages tagged with a specific keyword
not:<flag>not:deprecated reactExcludes deprecated packages from search results
is:<flag>is:unstableSurfaces prerelease or unstable alpha/beta packages
scope:<scope>scope:babelScrapes all packages published under a specific organizational scope
Composite querieskeywords:orm author:typeormCombines multiple operators for narrow targeting

✨ Key Features & Capabilities

  • ✅ Keyword search with qualifiers — Search npm using natural terms or advanced query operators such as keywords:orm, author:sindresorhus, or scope:babel.
  • ✅ Direct package list input — Pass exact package identifiers, including scoped modules (e.g. @babel/core, @nestjs/common, lodash).
  • ✅ Deep 1,000+ pagination — Uncapped pagination loops pull hundreds or thousands of packages per term without artificial restrictions (maxPagesPerSearch: 0 = automatic deep scan).
  • ✅ Verified maintainer emails — Collects direct maintainer and publisher contact details formatted as semicolon-delimited strings ready for CRM import.
  • ✅ Comprehensive download analytics — Pull verified download statistics over customizable windows (last-day, last-week, last-month).
  • ✅ Algorithmic health scores — Access official npm health metrics: popularityScore, qualityScore, maintenanceScore, and raw ranking finalScore.
  • ✅ Package footprint metrics — Captures unpacked disk size, published file counts, and dependency counts to audit package bloat.
  • ✅ Repository normalization — Cleans and normalizes source code URLs (git+, ssh://, Git shortcodes) into clickable HTTPS links.
  • ✅ Automated deduplication — Automatic name-based deduplication guarantees zero duplicate packages across multi-term runs.

📥 Input Parameters

The Actor accepts flexible inputs configured via simple JSON or the Apify Console form. All parameters are optional; running with default settings produces a fast sample run of popular packages.

ParameterTypeDefaultDescription
searchTermsarray["react"]Search keywords to query on npm. Supports qualifiers like keywords:cli or author:name.
packageNamesarray[]List of exact package names to fetch directly (e.g. ["express", "@angular/core"]).
includeDetailsbooleantrueFetch registry metadata: maintainer emails, repository links, dependencies, unpacked size.
includeDownloadsbooleantrueFetch official download counts for each package.
downloadPeriodstring"last-month"Time window for downloads: last-day, last-week, or last-month.
maxItemsinteger0Total packages to collect across all searches. 0 = unlimited (governed by search hits).
maxPagesPerSearchinteger0Maximum pages per search term (250 packages per page). 0 = unlimited pagination.
proxyConfigurationobject{ "useApifyProxy": true }Proxy configuration. Datacenter proxies are standard and cost-effective.

💡 Example Inputs

Example 1: Search and rank developer tools by downloads

{
"searchTerms": ["orm", "prisma", "drizzle"],
"includeDetails": true,
"includeDownloads": true,
"downloadPeriod": "last-month",
"maxItems": 500,
"maxPagesPerSearch": 0,
"proxyConfiguration": { "useApifyProxy": true }
}

Example 2: Audit specific dependencies and maintainer contacts

{
"packageNames": [
"express",
"@nestjs/core",
"fastify",
"@trpc/server",
"koa"
],
"includeDetails": true,
"includeDownloads": true,
"downloadPeriod": "last-month"
}

📤 Output Data Structure

The Actor pushes structured package records directly to the default dataset. Below is a real verified output item:

{
"name": "@testing-library/react",
"version": "16.3.3",
"description": "Simple and complete React DOM testing utilities that encourage good testing practices.",
"keywords": ["testing", "react", "ui", "dom", "jsdom", "unit", "integration", "functional", "e2e"],
"license": "MIT",
"downloads": 272678233,
"downloadPeriod": "last-month",
"homepage": "https://github.com/testing-library/react-testing-library#readme",
"repository": "https://github.com/testing-library/react-testing-library",
"npmUrl": "https://www.npmjs.com/package/@testing-library/react",
"bugsUrl": "https://github.com/testing-library/react-testing-library/issues",
"dependenciesCount": 1,
"devDependenciesCount": 13,
"unpackedSize": 339581,
"fileCount": 25,
"date": "2026-08-27T17:41:18.735Z",
"modifiedAt": "2026-08-27T17:41:18.735Z",
"author": "Kent C. Dodds",
"authorEmail": "me@kentcdodds.com",
"publisherUsername": "GitHub Actions",
"publisherEmail": "npm-oidc-no-reply@github.com",
"maintainers": [
{ "name": "kentcdodds", "email": "me@kentcdodds.com" },
{ "name": "timdeschryver", "email": "timdeschryver@outlook.com" },
{ "name": "eps1lon", "email": "silbermann.sebastian@gmail.com" }
],
"maintainerEmails": "me@kentcdodds.com; timdeschryver@outlook.com; silbermann.sebastian@gmail.com",
"popularityScore": 1,
"qualityScore": 1,
"maintenanceScore": 1,
"finalScore": 203.57,
"scrapedAt": "2026-11-10T14:22:10.120Z"
}

📊 Extracted Field Reference & Coverage

📦 Package Identity & Core Metadata

FieldTypeDescriptionCoverage
namestringCanonical package name (supports scopes like @scope/name)🟢 High (100%)
versionstringLatest semver release string🟢 High (100%)
descriptionstringShort summary provided by package author🟢 High (99%)
keywordsarrayDeclared ecosystem tags and categories🟡 Conditional (~70%)
licensestringNormalized SPDX license identifier (MIT, Apache-2.0, ISC, etc.)🟢 High (99%)
npmUrlstringDirect link to package page on npm🟢 High (100%)
homepagestringProject website or documentation URL🟢 High (98%)
repositorystringCleaned, clickable HTTPS source code repository link🟢 High (99%)
bugsUrlstringDirect link to issue tracker or bug submission page🟢 High (94%)

📈 Download Velocity & Algorithmic Scores

FieldTypeDescriptionCoverage
downloadsnumberAbsolute download count for the selected time window🟢 High (100%)
downloadPeriodstringEvaluated download period (last-day, last-week, last-month)🟢 High (100%)
popularityScorenumberOfficial npm popularity metric (0.0 to 1.0)🟢 High (100%)
qualityScorenumberOfficial npm code quality and test coverage score (0.0 to 1.0)🟢 High (100%)
maintenanceScorenumberOfficial npm maintenance and update cadence score (0.0 to 1.0)🟢 High (100%)
finalScorenumbernpm's composite search relevance ranking value🟢 High (100%)

👤 Maintainer Intelligence & Lead Generation

FieldTypeDescriptionCoverage
maintainersarrayArray of maintainer objects containing name and email🟢 High (100%)
maintainerEmailsstringSemicolon-delimited maintainer emails for instant CRM import🟢 High (99%)
publisherUsernamestringHandle of user or automated CI token that published the release🟢 High (100%)
publisherEmailstringVerified email of the releasing publisher🟢 High (99%)
authorstringDeclared package creator name🟡 Conditional (~55%)
authorEmailstringDeclared package creator email🟡 Conditional (~30%)

🏗️ Technical Footprint & Dependencies

FieldTypeDescriptionCoverage
dependenciesCountnumberNumber of runtime production dependencies🟢 High (100%)
devDependenciesCountnumberNumber of development dependencies🟢 High (100%)
unpackedSizenumberTotal disk footprint in bytes when installed🟢 High (99%)
fileCountnumberTotal count of files included in the tarball🟢 High (99%)
date / modifiedAtstringISO 8601 timestamp of latest published release🟢 High (100%)
scrapedAtstringISO 8601 timestamp of extraction execution🟢 High (100%)

🔁 Pagination & High-Volume Scraping

The scraper handles high-volume data harvesting seamlessly:

  1. Batch Fetching: The search pipeline requests 250 package records per batch from the official index.
  2. Infinite Pagination: When maxPagesPerSearch is set to 0, the scraper automatically advances offsets until all hits reported by the registry are exhausted or your maxItems target is fulfilled.
  3. Multi-Query Support: You can pass multiple queries in searchTerms (e.g. ["orm", "database", "sql"]); the scraper executes pagination across all queries while automatically pruning duplicates.
  4. Concurrent Enrichment: Metadata manifests and download metrics are retrieved concurrently in batches of 8, allowing extraction of 1,000+ packages in approximately 5–7 minutes.

🚀 How to Run the Scraper

Via Apify Console

  1. Navigate to the Actor page on Apify.
  2. Enter your desired search terms in Search terms or list specific packages in Package names.
  3. Choose your preferred download window (last-month, last-week, last-day).
  4. Set Max packages (maxItems) according to your quota (set 0 for complete category scraping).
  5. Click Start and monitor live execution logs.
  6. Export your final dataset in CSV, Excel, or JSON format.

Programmatically via Python

from apify_client import ApifyClient
# Initialize client with your Apify API token
client = ApifyClient("YOUR_APIFY_TOKEN")
# Configure input payload
run_input = {
"searchTerms": ["web framework", "backend"],
"downloadPeriod": "last-month",
"maxItems": 250,
"maxPagesPerSearch": 0,
"includeDetails": True,
"includeDownloads": True
}
# Run the Actor and fetch items
run = client.actor("haketa/npm-package-scraper").call(run_input=run_input)
dataset = client.dataset(run["defaultDatasetId"])
# Process top downloaded frameworks
for item in sorted(dataset.iterate_items(), key=lambda x: x.get("downloads") or 0, reverse=True):
print(f"{item['name']} (v{item['version']}) - {item['downloads']:,} downloads - Maintainers: {item['maintainerEmails']}")

Programmatically via Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('haketa/npm-package-scraper').call({
searchTerms: ['state management'],
downloadPeriod: 'last-month',
maxItems: 100,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.table(items.map(p => ({
name: p.name,
version: p.version,
downloads: p.downloads,
maintainerEmails: p.maintainerEmails,
unpackedSize: p.unpackedSize
})));

💡 Practical Scraping Tips

  • Prioritize Downloads Over Scores: While npm scores are helpful, popular mainstream packages frequently max out at 1.0. Use the downloads metric for fine-grained ranking and tiering.
  • Direct CRM Integration: Use the maintainerEmails field directly inside outreach tools or CRM platforms like HubSpot and Salesforce.
  • Targeted Ecosystem Searches: Use npm search qualifiers in searchTerms. For example, keywords:typescript will strictly pull packages tagged with TypeScript.
  • Audit Tarball Bloat: Compare unpackedSize against dependenciesCount to spot packages that introduce heavy disk footprints into production projects.
  • Automated Alerts: Set up weekly Apify scheduled runs to identify newly trending packages in your tech stack.

❓ Frequently Asked Questions

Does this Actor require an npm login or API key?
No. The Actor queries public package registry endpoints and download analytics. No credentials or paid API keys are required.

Can I scrape scoped packages?
Yes. Scoped packages like @babel/core, @types/node, or @angular/common are fully supported in both direct searches and keyword queries.

How is the repository URL normalized?
npm package manifests often store legacy URLs like git+https://... or ssh://git@github.com:.... This Actor automatically cleans these strings into standardized, browser-clickable HTTPS URLs.

What happens if a package has no download metrics?
New or unindexed packages will return null for downloads. The Actor handles this gracefully without interrupting the run.

Can I run this without downloading package details?
Yes. Disabling includeDetails and includeDownloads will only pull the search index summary, dramatically accelerating runs to thousands of packages per minute.

How fresh are the download metrics?
Download counts represent the official npm download statistics updated on daily cycles. Selecting last-month provides the most stable sample for adoption comparisons.

What is the difference between authorEmail, publisherEmail, and maintainerEmails?

  • authorEmail: The original author declared in package.json (may be individual developer or foundation).
  • publisherEmail: The account identity that executed npm publish for the latest version (often a CI bot or release lead).
  • maintainerEmails: The active team members authorized to push package updates, joined in a semicolon-separated string.

Can I export data automatically to Google Sheets or webhooks?
Yes. In Apify Console, configure an Apify Integration under the Integrations tab to push dataset rows directly to Google Sheets, Slack alerts, or custom webhook endpoints whenever an extraction finishes.

How does pagination handle queries with over 10,000 packages?
npm's public search index allows pagination across tens of thousands of records. With maxPagesPerSearch: 0, the Actor advances page offsets until maxItems is satisfied or all index results have been consumed.

Are duplicate packages filtered when querying multiple keywords?
Yes. An internal deduplication set checks canonical package names across all searches in real-time, ensuring you never receive duplicate records in your dataset.


🔌 Integrations & Export Options

The generated dataset integrates smoothly with popular data workflows:

  • Direct Downloads: Export cleanly formatted CSV, JSON, NDJSON, Excel (XLSX), and XML from the Apify storage UI.
  • REST API: Ingest data directly into your backend pipelines using Apify's standard REST API: GET https://api.apify.com/v2/datasets/{DATASET_ID}/items?format=json
  • Automation Platforms: Connect directly to Zapier, Make, and n8n to pipe newly identified packages into email sequences or internal spreadsheets.
  • Data Warehousing: Stream results into Snowflake, BigQuery, or PostgreSQL using Apify cloud storage connectors.


📋 Changelog

Version 1.2 (2026-11)

  • Deep 1,000+ Pagination Unlocked: maxPagesPerSearch updated to default to 0 (unlimited), allowing deep pagination up to thousands of packages per query.
  • Fast Execution: Optimized manifest lookups using lightweight per-version manifests (~2 KB) instead of heavy full history packuments, cutting run times by up to 75%.
  • Robust Repository URL Cleaning: Enhanced URL normalizer resolves SCP syntax and Git provider shorthands into standardized HTTPS URLs.
  • Schema Validation: Standardized all string output representations and upgraded dataset schema views for instant tabular inspection.

Version 1.1 (2026-10)

  • Added unpacked size and file count telemetry.
  • Concurrent batch enrichment for download counts.

Version 1.0 (2026-10)

  • Initial public release of npm Package Scraper with keyword search and maintainer lead extraction.