node-fetch
A light-weight module that brings Fetch API to node.js
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:browser.js | AI (source-diff): browser.js is a standard browser shim that re-exports native fetch globals using safe typeof checks. The Function() reference is only in a comment. No actual dynamic code execution or network calls present. | ai | |
| provenance | publisher-changed | AI (provenance): node-fetch-bot is the official publishing bot for the node-fetch org; transition from 'endless' is documented and has been stable since 2020. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() in a Proxy handler trap is standard JS — default forwarding behavior, not obfuscation. | ai | |
| provenance | no-provenance | AI (provenance): node-fetch is a long-established package; lack of provenance attestation is common and not a meaningful risk signal here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.3.2 | 3 / 16 | |
| 3.3.1 | 3 / 16 | |
| 3.3.0 | 3 / 16 | |
| 3.2.10 | 3 / 16 | |
| 2.6.13 | 1 / 26 | |
| 2.6.12 | 1 / 26 | |
| 2.6.11 | 1 / 26 | |
| 2.6.10 | 1 / 26 | |
| 2.6.9 | 1 / 26 | |
| 2.6.8 | 1 / 26 |
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.