Is node-fetch healthy, maintained, and safe?
No — node-fetch looks abandoned and still has open security advisories.
The verdict
On the OSPulse health scale, node-fetch lands at 9/100 — critical risk, computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — node-fetch looks abandoned and still has open security advisories.
The last sign of life was 23 August 2023, more than 2 years ago (1069 days); by any practical measure the package looks abandoned. Historically it released far more frequently, so the current silence reads as a genuine collapse in velocity rather than a natural gap. 5 maintainers are listed on npm, so the project isn't hostage to any single contributor.
OSV lists 3 known advisories for node-fetch, including 1 high. Review whether your version is in the affected range and whether a fixed release is available before depending on it. Each advisory is listed with its OSV/GHSA identifier below.
The safest reading is to replace, fork, or tightly pin node-fetch and stop taking on new exposure to it. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (3)
node-fetch forwards secure headers to untrusted sites
node-fetch Inefficient Regular Expression Complexity
The `size` option isn't honored after following a redirect in node-fetch
Key facts
- Latest version
- v3.3.2
- Last release
- 23 August 2023 (1069 days ago)
- Total releases
- 96
- First release
- 27 January 2015
- Package age
- 11.5 years
- Maintainers
- 5
- Known advisories
- 3
- Confidence
- High
Frequently asked
Is node-fetch still maintained?
It doesn't appear to be — the last release was 23 August 2023, over two years ago, which usually indicates an abandoned package.
Does node-fetch have known security vulnerabilities?
Yes — OSV lists 3 advisories for node-fetch. See the advisory list on this page for the OSV/GHSA identifiers.
Is node-fetch safe to use?
No — node-fetch looks abandoned and still has open security advisories. OSPulse rates it 9/100 (critical risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
node-fetch is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.