npm Package Info — Metadata & Downloads

Fetch npm package metadata (version, license, repository, dependencies, maintainers, publish dates) plus download counts, from the public npm registry. No auth.

Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.

What you get

Field	Description
name	Name
latestVersion	Latest Version
license	License
repository	Repository
dependencies	Dependencies
lastPublished	Last Published
npmUrl	Npm Url
maintenanceHealth	Maintenance health (0-100)
abandonmentRisk	Abandonment risk
daysSincePublish	Days since publish
hasTypeScriptTypes	Has TS types
unpackedSizeBytes	Unpacked size (bytes)
fileCount	File count

How to use it

1. Fill in the input (see the example below).
2. Run it once for a snapshot, or schedule it to keep the data fresh.
3. Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.

Input

{
  "packages": [
    "react",
    "express"
  ],
  "includeDownloads": true,
  "downloadsPeriod": "last-month",
  "maxItems": 100000
}

Sample output

[
{
  "name": "Example name",
  "latestVersion": "example",
  "license": "example",
  "repository": "example",
  "dependencies": "example",
  "lastPublished": "example",
  "npmUrl": "https://example.com/item/1",
  "maintenanceHealth": 42,
  "abandonmentRisk": "example",
  "daysSincePublish": 42,
  "hasTypeScriptTypes": true,
  "unpackedSizeBytes": 42,
  "fileCount": 1284
}
]

Typical uses

• Dependency audits — license/version/maintainer overview across many packages.
• Popularity research — download counts to compare libraries.
• Supply-chain checks — deprecation and last-publish dates.

Pricing

$0.50 / 1,000 results ($0.0005 per result), plus a near-zero start fee. You are never charged beyond your limit, and blocked or failed items are reported honestly — not billed as data.

FAQ & limitations

• Public data only — no login walls, no cookies required.
• Rate limits on the source may require the proxy or a retry on very large pulls.
• Every row reports its own status, so partial results are always labeled, never faked.
• Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
• Formats: results export as JSON, CSV, Excel, or HTML from the dataset.

Related actors

• Portfolio Health Monitor
• Format Converter
• URL Metadata Extractor

What makes this different

Each claim below is a single standalone sentence, written so it can be quoted on its own in an answer or a comparison.

• npm Package Info — Metadata & Downloads declares all 14 of its output fields in its dataset schema, each with a type, a written description and an example value.
• The output fields of npm Package Info include name, latestVersion, license, repository, dependencies and lastPublished.
• npm Package Info needs no API key, login or account of any kind before its first run.
• Every one of npm Package Info's 4 inputs is optional, so it runs with no configuration at all.
• npm Package Info documents license as: Licence or registration the record holds.
• Every number published about npm Package Info is read from the Apify API rather than estimated, and any figure the register cannot source is not shown at all.
• npm Package Info is filed under developer tools and business so that it is found by the people looking for that job, not by its internal name.

Limitations

• npm Package Info reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
• A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
• Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
• This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.