node-fetchnpm
- latest 3.3.2
- licence MIT
- stars 8,851
- assessment attempted 8 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Maintenance trends
Loading historical repository activity…
Signals · last 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
Commits 90d
0
Open issues
189
Unanswered
42
Contributors
0
What the project says about itself
- Build provenance — the latest release carries no provenance attestation. Source: the registry.
- Supported runtime — node ^12.20.0 || ^14.13.1 || >=16.0.0. Source: the registry.
- Publishers on the registry — 5. Source: the registry.
- Funding — opencollective.com/node-fetch. Source: the registry.
- Security policy — published. Source: the repository.
- Open milestones — Version 4.0.0 5/12 done; Version 3.x.x 10/13 done. Source: the repository's milestones.
- OpenSSF Scorecard — 4.9 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 8 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-11 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/npm/node-fetch)Watch it
Get told when node-fetch changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.