npm Registry Package Data Scraper

Exports flat JSON records for npm packages — latest version, license, dependency counts, maintainers, publish dates, and weekly downloads — by querying registry.npmjs.org directly. Built for developers vetting dependencies, SEO/content tools tracking package metadata, and lead-gen or research workflows that need structured data on npm packages at scale.

Why this scraper

• Covers the same fields as other npm-registry scrapers — license, dependencies, maintainers, downloads, quality/popularity/maintenance scores — with nothing missing from the standard set.
• Priced at $0.00003 per run, undercutting the $0.00005 charged by most comparable actors on the same per-run unit, and avoids per-result pricing that scales up fast on large searches.
• Reads straight from npm's public, keyless JSON API — no browser rendering, no auth, no session overhead — so there's no added cost or fragility from anti-bot workarounds that this source doesn't require.

Output fields

Field	Type	Description
packageName	string	npm package name, e.g. express
latestVersion	string	dist-tags.latest version string
description	string	Package description
license	string	License identifier, e.g. MIT
homepage	string	Package homepage URL
repositoryUrl	string	Source repository URL
keywords	string	Comma-joined keyword list
author	string	Primary author name
maintainersCount	integer	Number of listed maintainers
versionsCount	integer	Total published versions in the versions map
dependenciesCount	integer	Number of dependencies on the latest version
peerDependenciesCount	integer	Number of peerDependencies on the latest version
weeklyDownloads	integer	Downloads in the last week, from the npm downloads API
lastPublishedAt	string	ISO timestamp of the latest version's publish date
createdAt	string	ISO timestamp the package was first published
qualityScore	number	npm search quality score (search results only)
popularityScore	number	npm search popularity score (search results only)
maintenanceScore	number	npm search maintenance score (search results only)
sourceUrl	string	The startUrl this record was scraped from

Input

{
  "startUrls": [{ "url": "https://registry.npmjs.org/express" }],
  "maxItems": 50
}

You can also point startUrls at a search endpoint, e.g. https://registry.npmjs.org/-/v1/search?text=typescript&size=50, to pull multiple packages from one query. Set includeDownloads: false to skip the extra weekly-downloads lookup and reduce latency.

Output

{
  "packageName": "express",
  "latestVersion": "5.2.1",
  "description": "Fast, unopinionated, minimalist web framework",
  "license": "MIT",
  "homepage": "https://expressjs.com/",
  "repositoryUrl": "git+https://github.com/expressjs/express.git",
  "keywords": "express, framework, sinatra, web, http, rest, restful, router, app, api",
  "author": "TJ Holowaychuk",
  "maintainersCount": 5,
  "versionsCount": 288,
  "dependenciesCount": 28,
  "peerDependenciesCount": null,
  "weeklyDownloads": null,
  "lastPublishedAt": "2025-12-01T20:49:43.268Z",
  "createdAt": "2010-12-29T19:38:25.450Z",
  "qualityScore": null,
  "popularityScore": null,
  "maintenanceScore": null,
  "sourceUrl": "https://registry.npmjs.org/express"
}

Pricing

Pay per event: $0.00003 per Actor Start, charged once per run no matter how many startUrls or how large maxItems is. A typical run — one or several package lookups, or a single search query returning up to 50 results — costs $0.00003 total.

Use cases

• Dependency auditing: pull license, maintainer count, and last-publish date for every package in a package.json before a security or compliance review.
• Package research tools: build a dashboard or CLI that compares weekly downloads and dependency counts across candidate libraries before adoption.
• Ecosystem monitoring: track new versions and publish cadence for packages your product depends on, or for competitive analysis of libraries in your space.