node-releases
npmv2.0.54Node.js releases data
Safe to adopt
Yes — node-releases scores well across adoption, maintenance, weight, supply chain, and licensing. 186M downloads per week and 1 known dependents. Last published 13 days ago. 22 releases in the last 2 years.
- AAdoption: grade A, Excellent.
186M downloads per week and 1 known dependents.
- AMaintenance: grade A, Excellent.
Last published 13 days ago. 22 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 60 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding node-releases to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=18
- Module format
- ESM only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the node-releases README.
// CommonJS
const envs = require('node-releases/data/processed/envs.json');
const schedule = require('node-releases/data/release-schedule/release-schedule.json');
// ESM (Node.js 22+)
import envs from 'node-releases/data/processed/envs.json' with { type: 'json' };
import schedule from 'node-releases/data/release-schedule/release-schedule.json' with { type: 'json' };node-releases vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| node-releasesthis page | 186M | 1 | MIT | 13 days ago |
| sql-escaper | 4.9M | 1 | MIT | 5 days ago |
| @opentelemetry/api | 0 | 4 | Apache-2.0 | 5 days ago |
| @humanwhocodes/retry | 0 | 2 | Apache-2.0 | 5 days ago |
| fdir | 0 | 3 | MIT | 5 days ago |
| hono | 0 | 4 | MIT | 5 days ago |
Dependencies
Declared by node-releases v2.0.54. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (1)
Used by
Popular packages that depend on node-releases.
Relationship graph
Dependencies (left) and dependents (right) of node-releases.
Frequently installed together
A smaller version of caniuse-db, with only the essentials!
A library for obtaining browser versions with their maximum supported Baseline feature set and Widely Available status.
Provides a list of electron-to-chromium version mappings
CLI tool to update caniuse-lite to refresh target browsers from Browserslist config
Release history
22 releases in the last two years, typically about 12 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 2.0.54latest | 13 days ago | 60 KB | MIT |
| 2.0.53 | 1 month ago | 60 KB | MIT |
| 2.0.52 | 1 month ago | 60 KB | MIT |
| 2.0.51 | 2 months ago | 59 KB | MIT |
| 2.0.50 | 2 months ago | 59 KB | MIT |
| 2.0.49 | 2 months ago | 59 KB | MIT |
| 2.0.48 | 2 months ago | 59 KB | MIT |
| 2.0.47 | 3 months ago | 59 KB | MIT |
| 2.0.46 | 3 months ago | 58 KB | MIT |
| 2.0.45 | 3 months ago | 58 KB | MIT |
| 2.0.44 | 4 months ago | 41 KB | MIT |
| 2.0.42 | 4 months ago | 41 KB | MIT |
| 2.0.38 | 4 months ago | 41 KB | MIT |
| 2.0.37 | 5 months ago | 41 KB | MIT |
| 2.0.36 | 6 months ago | 41 KB | MIT |
Overview
node-releases is an npm package that node.js releases data. It is extremely widely used, with about 186M downloads per week and 1 known dependents in the graph. The latest version is 2.0.54, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need node.js releases data and value a battle-tested, widely-adopted solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Large, well-established user base (186M weekly downloads).
- Clear open-source license (MIT).
- Lean dependency tree (1 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use node-releases?
Yes — node-releases scores well across adoption, maintenance, weight, supply chain, and licensing. 186M downloads per week and 1 known dependents. Last published 13 days ago. 22 releases in the last 2 years.
How do I install node-releases?
Run `npm install node-releases` to add node-releases to your npm project.
What license is node-releases released under?
node-releases is distributed under the MIT license.
How popular is node-releases?
node-releases has approximately 186,011,412 downloads per week and 1 known dependent packages.
Is node-releases still maintained?
The most recent release of node-releases (v2.0.54) was published 13 days ago.
Does node-releases run install scripts?
No. node-releases does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.