d3-shape
Graphical primitives for visualization, such as lines and areas.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): recifs is the D3 organization npm account; the mbostock→recifs transition in 2020 is a well-known legitimate governance change across the entire D3 ecosystem. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed back to mbostock, the canonical author of d3-shape and creator of D3. This is a legitimate maintainer transition, not a compromise. Generalizes stably for this package. | ai | |
| provenance | no-provenance | AI (provenance): d3-shape predates Sigstore provenance attestation; absence of attestation is expected for this package's publishing history. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 1 / 5 | |
| 3.1.0 | 1 / 5 | |
| 3.0.1 | 1 / 5 | |
| 3.0.0 | 1 / 5 | |
| 2.1.0 | 1 / 5 | |
| 2.0.0 | 1 / 5 | |
| 1.3.7 | 1 / 5 | |
| 1.3.6 | 1 / 5 | |
| 1.3.5 | 1 / 5 | |
| 1.3.4 | 1 / 5 | |
| 1.3.3 | 1 / 5 | |
| 1.3.2 | 1 / 5 | |
| 1.3.0 | 1 / 5 | |
| 1.2.3 | 1 / 5 | |
| 1.2.2 | 1 / 5 | |
| 1.2.1 | 1 / 5 | |
| 1.2.0 | 1 / 6 | |
| 1.1.1 | 1 / 6 | |
| 1.1.0 | 1 / 6 | |
| 1.0.6 | 1 / 6 | |
| 1.0.5 | 1 / 6 | |
| 1.0.4 | 1 / 6 | |
| 1.0.3 | 1 / 6 | |
| 1.0.2 | 1 / 6 | |
| 1.0.1 | 1 / 6 | |
| 1.0.0 | 1 / 6 | |
| 0.7.1 | 1 / 6 | |
| 0.7.0 | 1 / 6 | |
| 0.6.1 | 1 / 6 | |
| 0.6.0 | 1 / 5 | |
| 0.5.1 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.4.0 | 1 / 5 | |
| 0.3.0 | 1 / 5 | |
| 0.2.2 | 1 / 5 | |
| 0.2.1 | 1 / 5 | |
| 0.2.0 | 1 / 5 | |
| 0.1.0 | 1 / 4 | |
| 0.0.3 | 1 / 4 | |
| 0.0.2 | 1 / 4 | |
| 0.0.1 | 1 / 4 |
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsThis version was published by a different npm account than previous versions on 2021-03-10. 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-19. This could indicate a legitimate maintainer transition or an account compromise.