npm Package Metadata Batch Export

Export latest public npm package versions, declared licenses and dependency metadata from a supplied package list.

What can this tool do?

Turn a supplied dependency list into a version-and-license inventory for a workflow or spreadsheet.

What data does it return?

The default dataset contains JSON rows with these overview fields: id, status, packageName, version, licenseDeclared, dependencyCount, dependencies, nodeEngine, sourceUrl. RESULTS_CSV contains the rows delivered by this run; OUTPUT records completion, warnings and stop reason. CHECKPOINT supports best-effort resume. A completed checkpoint makes no new source request; use a fresh input without it for a fresh snapshot.

How to use it

Provide the source inputs below. Run it through Apify, then inspect OUTPUT before consuming a partial export. If a result or request cap is reached, reuse CHECKPOINT with the same source inputs; resuming does not repeat rows already acknowledged by this export. Source changes can still move search results between pages, so it is not a historical snapshot guarantee.

{
  "packages": [
    "express",
    "react"
  ],
  "maxResults": 2,
  "maxRequests": 2
}

Only the latest manifest is read. License fields are publisher declarations, not legal clearance. This does not install packages, resolve a full dependency tree, audit vulnerabilities, export maintainer contacts or download artifacts. A maximum of 10 package requests per run means larger lists require checkpoints.

Pricing

Runs can incur Apify charges. Check the current Store pricing and spending limit before starting. Result fees apply to successfully delivered records; package notFound status rows have no result fee, although a startup fee may still apply. No synthetic default-dataset charge is used in addition to the record event.

The npm registry API is free to query directly; this Actor adds Apify run controls, saved datasets, checkpoints and CSV.

Is it legal?

Uses documented npm public registry APIs with bounded requests. No npm website crawling, personal contact export or npm security-report redistribution. Follow npm terms and each package license; a declared license does not prove permission for every use. No affiliation or endorsement is implied.

Source documentation: https://github.com/npm/registry/blob/main/docs/REGISTRY-API.md Policy/context: https://docs.npmjs.com/policies/open-source-terms/

FAQ

Does it retry blocks or bypass authentication? No. Source HTTP errors stop without retries; source hosts are fixed and redirects are not followed.

Are unknown values zero? No. Unavailable fields stay null or cause an explicit source error. Read the source-specific limits above.

Is the data exclusive? No. The official source is public and has a free native alternative.

Feedback

Use the Actor Issues tab with a small reproducible public example and the OUTPUT stop reason. Do not post tokens, personal records or confidential data.