← Rankings

node-fetch

npm · Rank #25 of 116

85 / 100 B
STALE — No release in 881 days. Stale packages accumulate unpatched vulnerabilities.
5
npm publishers
Distributed credential risk
135M
downloads/week
Blast radius if compromised
11.3y
package age
Established package
881 days ago
last release
Possibly unmaintained

Risk analysis

node-fetch has not published a release in over 12 months. Stale packages accumulate vulnerabilities and may indicate abandonment.

What the score measures

  • Publisher depth — How many people can push to npm? Single-publisher packages are the #1 structural risk.
  • Longevity — Older packages have track records. New packages with high adoption are higher risk.
  • Release consistency — Regular releases signal active oversight. Long gaps mean unpatched vulnerabilities.
  • Download trend — Growing packages attract more scrutiny (and more attacks).
  • OpenSSF Scorecard — Process security: branch protection, code review, CI/CD safety.

node-fetch is one package. Score them all.

You came looking for node-fetch. Your node_modules has hundreds more. Run one command to score every dependency you ship:

npx proof-of-commitment

Auto-detects your lockfile. Scores every dependency. Zero install.

Add the badge to your README

Commit trust score for node-fetch
![Commit Trust](https://getcommit.dev/badge/npm/node-fetch)