cross-fetch
Universal WHATWG Fetch API for Node, Browsers and React Native
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 | obfuscated-file:dist/fetch-browser-polyfill.js | AI (source-diff): This is a standard minified whatwg-fetch polyfill bundle. Shipping minified browser dist files is the expected behavior of cross-fetch; no malicious patterns present. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is explained by addition of minified browser dist bundles, a normal step in cross-fetch's release process. | ai | |
| source-diff | obfuscated-file:dist/fetch-browser.js | AI (source-diff): Standard minified fetch polyfill bundle for browser environments. Expected dist artifact for cross-fetch; code is readable fetch API implementation, not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/cross-fetch.js | AI (source-diff): dist/cross-fetch.js is the expected minified whatwg-fetch browser polyfill — the core deliverable of this package. Long lines are from minification, not obfuscation. Stable false positive for cross-fetch. | ai | |
| dependencies | unvetted-dep:fetch-ponyfill | AI (dependencies): fetch-ponyfill is a legitimate, well-known Fetch API ponyfill package; its use is core to cross-fetch's purpose and stable across versions. | ai | |
| dependencies | unvetted-dep:node-fetch | AI (dependencies): node-fetch is a well-known, widely-used HTTP library and a legitimate dependency for cross-fetch; this finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:whatwg-fetch | AI (phantom-deps): whatwg-fetch is a browser polyfill referenced in bundling config for cross-fetch's browser build; not directly imported at runtime. This is expected and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): cross-fetch is a long-established package (2509 days); lack of Sigstore provenance is expected for packages predating the attestation ecosystem and is not a risk signal here. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 4.1.0 | 1 / 31 | |
| 4.0.0 | 1 / 30 | |
| 3.2.0 | 1 / 31 | |
| 3.1.8 | 1 / 31 | |
| 3.1.7 | 1 / 31 | |
| 3.1.6 | 1 / 31 | |
| 3.1.5 | 1 / 29 | |
| 3.1.4 | 1 / 29 | |
| 3.1.3 | 1 / 29 | |
| 3.1.2 | 1 / 25 | |
| 3.1.1 | 1 / 22 | |
| 3.1.0 | 1 / 21 | |
| 3.0.6 | 1 / 18 | |
| 3.0.5 | 1 / 18 | |
| 3.0.4 | 2 / 17 | |
| 3.0.3 | 2 / 17 | |
| 3.0.2 | 2 / 16 | |
| 3.0.1 | 2 / 16 | |
| 3.0.0 | 2 / 16 | |
| 2.2.6 | 2 / 18 | |
| 2.2.5 | 2 / 18 | |
| 2.2.4 | 2 / 18 | |
| 2.2.3 | 2 / 18 | |
| 2.2.2 | 2 / 18 | |
| 2.2.1 | 2 / 18 | |
| 2.2.0 | 2 / 16 | |
| 2.1.1 | 2 / 17 | |
| 2.1.0 | 2 / 14 | |
| 2.0.0 | 2 / 10 | |
| 1.1.1 | 2 / 9 | |
| 1.1.0 | 2 / 9 | |
| 1.0.0 | 2 / 9 | |
| 0.0.8 | 2 / 9 | |
| 0.0.7 | 2 / 10 | |
| 0.0.6 | 2 / 10 | |
| 0.0.5 | 3 / 5 | |
| 0.0.4 | 3 / 5 | |
| 0.0.3 | 3 / 5 | |
| 0.0.2 | 2 / 5 |
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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.0.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.
v2.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.