npm Registry Intel: Packages, Releases & Maintainer Leads

Pricing

Rating

Developer

Actor stats

Categories

Share

Turn the public npm registry into structured, B2B-ready data. Discover packages by keyword or scope, monitor releases across any package list, or build developer lead lists from maintainer contact emails. Built on the official public npm API: no proxy, no authentication, no rate-limit keys.

Who uses this

• Developer-tool and SaaS teams doing competitive intel: who ships in your category, how fast they release, how much reach they have.
• Recruiters and dev-relations teams sourcing maintainers of widely-installed packages (high-intent technical leads with public contact emails).
• Security and supply-chain analysts mapping dependency footprints and watching for new releases.
• Investors and market researchers sizing an ecosystem by download volume and release cadence.

Modes

1. Search packages (discovery / intel)

Find packages by free-text query or qualifiers (keywords:, scope:, author:, maintainer:). Each result carries the package name, version, description, keywords, license, maintainer names and emails, repository, homepage, and npm quality / popularity / maintenance scores. Enable enrichment to add weekly downloads, created date, latest release date, version count, and dependency count. Filter by minimum downloads to keep only packages with real traction.

2. Package deep-dive / release monitor

Pass an explicit list of package names to pull full metadata and download counts for each. In delta mode this becomes a release monitor: only packages whose latest version changed since the previous run are emitted, with the previous version included. Pair with a schedule and a webhook to get alerts when a dependency or a competitor ships.

3. Maintainer leads

Pass an npm username to list every package that maintainer publishes, always enriched with contact email, repository, and download reach. A maintainer of widely-installed packages is a strong technical lead for recruiting, dev-tool sales, or partnerships.

Delta / monitor mode

Every mode supports deltaMode. State is kept per account between runs:

• Search / maintainer: only packages that newly appear are emitted.
• Package: only packages whose latest version changed are emitted.

This makes the actor a recurring monitor rather than a one-shot scrape, which is the recurring-usage pattern you want behind a schedule.

Example input

{
"mode":"search",
"keywords":"payments",
"minDownloads":5000,
"downloadsPeriod":"last-week",
"maxItems":50
}

{
"mode":"package",
"packages":["express","fastify","@aws-sdk/client-s3"],
"deltaMode":true
}

{
"mode":"maintainer",
"maintainer":"sindresorhus",
"maxItems":100
}

Output fields

name, version, description, keywords, license, publisherEmail, publisherUsername, maintainers (name + email), author, authorEmail, homepage, repository, npmUrl, weeklyDownloads, createdAt, modifiedAt, latestPublishedAt, versionsCount, dependenciesCount, and npm scorePopularity / scoreQuality / scoreMaintenance.

Part of the B2B data suite

Combine with our other no-proxy intel actors for a full founder / VC / sales / dev dataset:

• GitHub Intel: repositories, developer leads, stargazers / contributors.
• Hacker News Intel: Who is Hiring jobs, Show HN launches, keyword monitor.
• Y Combinator Companies Scraper: startups by batch and industry.
• IndieHackers Product Scraper: products, revenue, founders.
• BetaList Startup Scraper: upcoming startup launches and makers.
• SEC EDGAR Intel: filings, XBRL financials, full-text search.

Notes

• Data comes from the official public npm registry (registry.npmjs.org) and download API (api.npmjs.org). No login or API key is required.
• Email addresses are those published by maintainers in public package metadata. Use them in line with applicable anti-spam and data-protection rules.