d3-fetch
Convenient parsing for Fetch.
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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): d3-fetch is a core d3 ecosystem package; missing gitHead reflects a publish environment change, not a compromise. Trusted publisher. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): recifs is a known d3 org collaborator (Philippe Rivière); legitimate maintainer transition from mbostock within the d3 project. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from recifs to mbostock (Mike Bostock, D3 creator). This is a legitimate transition within the D3 ecosystem. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2021 before Sigstore provenance was standard practice. Not a security concern for this established package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 1 / 4 | |
| 3.0.0 | 1 / 4 | |
| 2.0.0 | 1 / 4 | |
| 1.2.0 | 1 / 4 | |
| 1.1.2 | 1 / 4 | |
| 1.1.1 | 1 / 4 | |
| 1.1.0 | 1 / 5 | |
| 1.0.1 | 1 / 5 | |
| 1.0.0 | 1 / 5 | |
| 0.1.0 | 1 / 5 | |
| 0.0.2 | 1 / 5 | |
| 0.0.1 | 1 / 5 |
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-04. 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.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-08-23. This could indicate a legitimate maintainer transition or an account compromise.