NPM Package Version Monitor – npm package version and release data export

Give it a list of public npm package names, such as express or @types/node, and get back one row per package. Each row has the latest version, when it was published, how many days ago that was, the licence, whether the package is deprecated, and a short list of recent releases.

It reads the official public npm registry API (registry.npmjs.org), so you need no login or API key. Schedule it to run daily or weekly and compare latestVersion between runs to catch new releases of the libraries you depend on.

Why this one

• Official source. Every record comes straight from the public npm registry, not from a third-party mirror.
• One clean row per package. You get version, release dates, licence, deprecation status, repository URL and dependency count in a flat structure that opens neatly in a spreadsheet.
• Staleness at a glance. daysSinceLatestRelease tells you how long it has been since the last release, so you don't need to do the date maths.
• Scoped names work. Names like @types/node are handled, duplicates are removed and invalid names are skipped.
• No credentials needed. Only public package metadata is collected.
• Pay per result. $1.00 per 1,000 results, with no start fee, and runs with no results cost nothing.

Quick start

{
  "packages": ["express", "lodash", "@types/node"],
  "maxPackages": 5,
  "maxVersionsPerPackage": 5
}

This returns one record for each of the three packages, including the five most recent versions of each with their publish timestamps.

What you can use it for

Who	What for
Engineering teams	Watch the libraries your product depends on and spot stale or deprecated packages early
DevOps and platform teams	Schedule a run and compare latestVersion between runs to detect new releases of key frameworks
Security and compliance	Check license, isDeprecated and release cadence for packages under review
Open-source evaluators	Compare release frequency, versionsCount and maintainersCount before choosing a package
Analysts and managers	Export a table of package health indicators to spreadsheets or dashboards

How to use it

1. Click Try for free.
2. In Package names, add the npm packages you want to check, for example express, lodash or @types/node. Invalid names are skipped and duplicates are removed.
3. Set Maximum packages (1 to 100, default 20). Names beyond this limit are ignored.
4. Set Recent versions per package (0 to 50, default 5) to choose how many releases appear in recentVersions. Use 0 if you only want the latest version.
5. Click Start.
6. To track new releases, create a schedule and compare latestVersion or latestPublishedAt between runs.

What data you get

Each record describes one package. Example values are from a test run on 26 Oct 2026.

Field	What it is	Example
id	Stable ID for the package	npm:express
packageName	The npm package name	express
url	npmjs.com page for the package	https://www.npmjs.com/package/express
registryUrl	Registry API address the data came from	https://registry.npmjs.org/express
latestVersion	Version tagged as latest	5.3.0
latestPublishedAt	When the latest version was published	2026-10-09T12:56:54.505Z
daysSinceLatestRelease	Days since the latest release	16
createdAt	When the package was first created	2010-12-29T19:38:25.450Z
modifiedAt	When the registry record last changed	2026-10-09T12:56:55.078Z
versionsCount	Number of published versions	290
distTags	Dist-tags mapped to versions	{"latest": "5.3.0", "latest-4": "4.22.3"}
isDeprecated	Whether the latest version is deprecated	false
deprecationMessage	Deprecation notice, if any	null
license	Licence identifier	MIT
description	Short package description	Fast, unopinionated, minimalist web framework
keywords	Keywords listed by the package	["express", "framework", "web"]
homepage	Package homepage	https://expressjs.com/
repositoryUrl	Normalised repository URL	https://github.com/expressjs/express
maintainersCount	Number of maintainers (names are not exported)	5
dependenciesCount	Number of runtime dependencies	28
nodeEngine	Declared Node.js engine range	>= 18
recentVersions	Most recent versions with publish times	[{"version": "5.3.0", "publishedAt": "2026-10-09T12:56:54.505Z"}]
fetchedAt	When this record was fetched	2026-10-26T10:17:51.960Z

Pricing

Event	Price
Result (one package record)	$0.001

Run	Cost
100 results	$0.10
1,000 results	$1.00
10,000 results	$10.00

There is no start fee. Runs with no results cost nothing.

Good to know

• Limits. A run processes up to 100 packages, and recentVersions lists up to 50 versions per package.
• Data source. All data comes from the public npm registry at registry.npmjs.org. Only public package metadata is collected.
• Missing packages. Names that don't exist are skipped, so you are only charged for real results.
• Privacy. Maintainer names and email addresses are not exported, only the count.
• Freshness. Data reflects the registry at fetch time (see fetchedAt) and may lag briefly behind npm replication.
• Large packages. Packages with very large registry documents can take longer to fetch.
• Not affiliated. This tool isn't affiliated with or endorsed by npm or GitHub.

FAQ

Do I need an npm account or API key? No. The tool reads public registry data only.

Can I check scoped packages? Yes. Enter names like @types/node in Package names.

What happens if I enter a package that doesn't exist? It is skipped and not charged.

How do I find out when a package has a new release? Schedule the tool and compare latestVersion or latestPublishedAt between runs.

Getting the data out

Download results as Excel, CSV or JSON from the Output tab. Send them to Google Sheets, Slack, Zapier, Make or webhooks from the Integrations tab. Every run is also available through the Apify API, and you can schedule runs from Schedules.

Questions or problems

Open an issue on the Issues tab and include the run link. I reply within one business day.

Related tools

• GitHub Public Issue Monitor: track issues on public GitHub repositories
• GitHub Public Release Monitor: watch releases on public GitHub repositories
• PyPI Package Release Monitor: the same kind of version check for Python packages