whatwg-fetch
A window.fetch polyfill.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from mislav to jakechampion is a documented legitimate maintainer transition at the GitHub org level; jakechampion has a long, clean track record with 51 approved versions. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): jakechampion is a known GitHub employee who took over maintenance of the github/fetch repo; this is a legitimate organizational handoff, not a compromise. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 3.6.20 | 0 / 17 | |
| 3.6.19 | 0 / 17 | |
| 3.6.18 | 0 / 17 | |
| 3.6.17 | 0 / 16 | |
| 3.6.16 | 0 / 16 | |
| 3.6.15 | 0 / 16 | |
| 3.6.14 | 0 / 16 | |
| 3.6.13 | 0 / 16 | |
| 3.6.12 | 0 / 16 | |
| 3.6.11 | 0 / 16 | |
| 3.6.10 | 0 / 16 | |
| 3.6.9 | 0 / 16 | |
| 3.6.8 | 0 / 16 | |
| 3.6.7 | 0 / 16 | |
| 3.6.6 | 0 / 17 | |
| 3.6.5 | 0 / 17 | |
| 3.6.4 | 0 / 17 | |
| 3.6.3 | 0 / 17 | |
| 3.6.2 | 0 / 17 | |
| 3.6.1 | 0 / 17 | |
| 3.6.0 | 0 / 17 | |
| 3.5.0 | 0 / 17 | |
| 3.4.1 | 0 / 17 | |
| 3.4.0 | 0 / 17 | |
| 3.3.1 | 0 / 17 | |
| 3.3.0 | 0 / 17 | |
| 3.2.0 | 0 / 17 | |
| 3.1.1 | 0 / 17 | |
| 3.1.0 | 0 / 17 | |
| 3.0.1 | 0 / 17 | |
| 3.0.0 | 0 / 16 | |
| 2.0.4 | 0 / 6 | |
| 2.0.3 | 0 / 6 | |
| 2.0.2 | 0 / 6 | |
| 2.0.1 | 0 / 6 | |
| 2.0.0 | 0 / 6 | |
| 1.1.1 | 0 / 6 | |
| 1.1.0 | 0 / 6 | |
| 1.0.0 | 0 / 6 | |
| 0.11.1 | 0 / 6 | |
| 0.11.0 | 0 / 6 | |
| 0.10.1 | 0 / 6 | |
| 0.10.0 | 0 / 6 | |
| 0.9.0 | 0 / 6 | |
| 0.8.2 | 0 / 6 | |
| 0.8.1 | 0 / 6 | |
| 0.8.0 | 0 / 6 | |
| 0.7.0 | 0 / 6 | |
| 0.6.1 | 0 / 6 | |
| 0.6.0 | 0 / 6 | |
| 0.5.0 | 0 / 6 |
v3.6.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
2 findingsThis version was published by a different npm account than previous versions on 2020-06-29. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version was published by a different npm account than previous versions on 2020-07-08. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.