npm Package Data — Metadata & Download Stats avatar

npm Package Data — Metadata & Download Stats

Pricing

from $1.44 / 1,000 packages

Go to Apify Store
npm Package Data — Metadata & Download Stats

npm Package Data — Metadata & Download Stats

Get npm package data: latest version, description, license, repository, author, keywords, dependency count, publish dates and download counts. Powered by the official npm registry. No API key, no anti-bot.

Pricing

from $1.44 / 1,000 packages

Rating

0.0

(0)

Developer

Marouane Oulabass

Marouane Oulabass

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Categories

Share

npm Package Data — Registry Info & Download Stats to JSON

Get clean data for any npm package — as JSON. Pass package names and get back a tidy row per package: latest version, description, license, repository, author, keywords, dependency count, publish dates and download counts. Powered by the official npm registry — no API key, no anti-bot.

AI-agent ready: this Actor is callable and payable by AI agents via x402 (USDC on Base), no Apify account required.

Skip scraping npmjs.com — pull structured package data for dashboards, research and supply-chain analysis in one run.

Who uses this

  • 🧑‍💻 Developers & OSS maintainers — inventory and compare packages.
  • 📊 Analysts & researchers — study download trends, licenses and dependencies at scale.
  • 🔐 Security & supply-chain teams — audit dependencies, licenses and maintainers.
  • 🤖 Data & AI pipelines — feed clean package metadata into your tooling.
  • 📈 DevRel & competitive intel — track a package's popularity over time.

What you get — one clean row per package

FieldDescription
name + latestVersionPackage & current version
descriptionPackage description
licenseLicense (e.g. MIT)
repository + homepageSource & site links
author + maintainersCountAuthor & maintainers
keywordsPackage keywords
dependenciesCount + dependenciesDependencies
versionsCountNumber of published versions
created + lastPublishFirst & last publish dates
downloads + downloadsPeriodLabelDownload counts (optional period)
npmUrlLink to the npm page

Example

Input

{ "packages": ["react", "express", "lodash"], "downloadsPeriod": "last-month" }

Output (one item)

{
"name": "react", "latestVersion": "19.1.0",
"description": "React is a JavaScript library for building user interfaces.",
"license": "MIT", "author": "Meta",
"dependenciesCount": 1, "versionsCount": 2200,
"lastPublish": "2026-06-20T12:00:00Z",
"downloads": 24500000, "downloadsPeriodLabel": "last-month",
"npmUrl": "https://www.npmjs.com/package/react"
}

Why this actor

  • Official source — the npm registry, always current.
  • 📦 Rich metadata — version, license, deps, maintainers, dates.
  • 📈 Optional download stats — add a period to fetch download counts.
  • Fast & affordable — pay only per package returned. No key, no anti-bot.
  • 🧹 Clean output — normalized JSON, ready for Sheets/Excel/your database.

Input options

  • packages (required) — npm package names.
  • downloadsPeriod — optional download window (e.g. last-week, last-month).

FAQ

Do I get download counts? Optionally — set downloadsPeriod to include them (adds a call per package).

Which data is included? Version, description, license, repository, author, keywords, dependency and version counts, and publish dates.

How fresh is the data? Live from the npm registry on every run.

Can I query many packages at once? Yes — pass a list; every row carries its own package name.

Can I export to CSV/Excel/Google Sheets? Yes — the dataset exports to JSON, CSV, Excel and HTML, or pull it via the API.

What does it cost? Pay-per-package — you're only charged for packages actually returned.


Tip: track your dependencies weekly and diff latestVersion/downloads to monitor updates and momentum.