npm Package Info — Metadata, Downloads & Health
Fetch npm package metadata (version, license, repository, dependencies, maintainers, publish dates) plus download counts, from the public npm registry. No auth.
npm Package Info — Metadata, Downloads & Health returns 14 documented output fields, including name, latestVersion, license, repository and dependencies. Every field carries a declared type, a written description and an example value. 33 runs are recorded on Apify.
- 14
- Output fields
- 4
- Inputs
- 33
- Runs
- 2026-10-15
- Last run
01 — output
What it returns
Every field the extractor writes to its dataset, with its type, a written description and an example value.
| Field | Type | What it holds | Example |
|---|---|---|---|
| name | stringnull | Display name as the source writes it. | Bitcoin |
| latestVersion | stringnull | Most recent version published upstream. | 4.2.1 |
| license | stringnull | Licence or registration the record holds. | MIT |
| repository | stringnull | Source repository URL. | <repository> |
| dependencies | integernull | Number of dependencies. | 0 |
| lastPublished | stringnull | ISO 8601 timestamp of the most recent publication. | <lastPublished> |
| npmUrl | stringnull | Link to this package on npm. | <npmUrl> |
| maintenanceHealth | integernull | Maintenance health on a 0-100 scale. | 74 |
| abandonmentRisk | stringnull | How likely this project is to be abandoned, in words. | low |
| daysSincePublish | integernull | Days elapsed since publication. | 0 |
| hasTypeScriptTypes | booleannull | Whether the package ships its own type definitions. | true |
| unpackedSizeBytes | integernull | Unpacked size in bytes. | 0 |
| fileCount | integernull | File Count as recorded for this row. | 0 |
| deprecated | booleannull | Whether this is marked deprecated upstream. | true |
02 — sample
One record
Assembled from the example values declared on the schema above, not invented at render time.
{
"name": "Bitcoin",
"latestVersion": "4.2.1",
"license": "MIT",
"repository": "<repository>",
"dependencies": 0,
"lastPublished": "<lastPublished>",
"npmUrl": "<npmUrl>",
"maintenanceHealth": 74
}03 — input
What you give it
| Input | Type | Description |
|---|---|---|
| packages | arrayrequired | npm package names (scoped ok, e.g. @types/node). |
| includeDownloads | booleanoptional | Fetch download stats per package. |
| downloadsPeriod | stringoptional | last-day, last-week, or last-month. |
| maxItems | integeroptional | Hard cap. |
04 — run
Run npm Package Info on your own input
It runs in the cloud on Apify. Nothing to install, and you are billed per result returned rather than per attempt.
05 — questions
Asked before running it
14 of 14 fields described
- What does npm Package Info — Metadata, Downloads & Health return?
- It returns 14 documented output fields: name, latestVersion, license, repository, dependencies, lastPublished, npmUrl, maintenanceHealth, abandonmentRisk, daysSincePublish, hasTypeScriptTypes and unpackedSizeBytes. Each field declares its type, a description of what it holds, and an example value. The remaining 2 are listed in the output schema below.
- What input does npm Package Info — Metadata, Downloads & Health require?
- packages is required. A further 3 inputs are optional. The full input schema, with types and defaults, is below.
- Does npm Package Info — Metadata, Downloads & Health need an API key or login?
- No. None of its inputs is a credential, and it reads only public data. Nothing to sign up for before the first run.
- How do I run npm Package Info — Metadata, Downloads & Health?
- It runs on Apify. Start it from its listing with the inputs above, or call the Apify API with the Actor's ID. Results land in a dataset you can export as JSON, CSV or Excel, or read through the Apify API into your own pipeline.