d3-path
Serialize Canvas path commands to SVG.
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 a known D3 ecosystem maintainer (Philippe Rivière); this is a documented legitimate transition from mbostock, stable across all d3-path versions. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead reflects a publish environment change during the D3 maintainer transition, not a security concern for this well-established package. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher changed from recifs back to mbostock, the original D3 author. mbostock has 1363 approved packages and is the canonical maintainer of all d3-* modules. This transition is legitimate. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 3.1.0 | 0 / 4 | |
| 3.0.1 | 0 / 4 | |
| 3.0.0 | 0 / 4 | |
| 2.0.0 | 0 / 4 | |
| 1.0.9 | 0 / 4 | |
| 1.0.8 | 0 / 4 | |
| 1.0.7 | 0 / 4 | |
| 1.0.6 | 0 / 4 | |
| 1.0.5 | 0 / 5 | |
| 1.0.4 | 0 / 5 | |
| 1.0.3 | 0 / 5 | |
| 1.0.2 | 0 / 5 | |
| 1.0.1 | 0 / 5 | |
| 1.0.0 | 0 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.1.5 | 0 / 4 | |
| 0.1.4 | 0 / 4 | |
| 0.1.3 | 0 / 4 | |
| 0.1.2 | 0 / 4 | |
| 0.1.1 | 0 / 4 | |
| 0.1.0 | 0 / 4 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 4 |
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
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.
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.