d3-axis
Displays automatic reference lines for scales.
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 | publisher-changed | AI (provenance): mbostock → recifs is a documented, legitimate D3 ecosystem maintainer transition. recifs has a long, clean track record and is the known steward of D3 modules. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): recifs addition is part of the known D3 maintainer transition; not a suspicious takeover. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with a changed publish environment during maintainer transition; no other malicious indicators present. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 8 | |
| 2.1.0 | 0 / 7 | |
| 2.0.0 | 0 / 7 | |
| 1.0.12 | 0 / 7 | |
| 1.0.11 | 0 / 7 | |
| 1.0.10 | 0 / 7 | |
| 1.0.9 | 0 / 8 | |
| 1.0.8 | 0 / 8 | |
| 1.0.7 | 0 / 6 | |
| 1.0.6 | 0 / 6 | |
| 1.0.5 | 0 / 6 | |
| 1.0.4 | 0 / 6 | |
| 1.0.3 | 0 / 6 | |
| 1.0.2 | 0 / 6 | |
| 1.0.1 | 0 / 6 | |
| 1.0.0 | 0 / 6 | |
| 0.4.1 | 0 / 6 | |
| 0.4.0 | 0 / 6 | |
| 0.3.2 | 3 / 5 | |
| 0.3.1 | 3 / 4 | |
| 0.3.0 | 3 / 4 | |
| 0.2.3 | 2 / 4 | |
| 0.2.2 | 2 / 4 | |
| 0.2.1 | 2 / 4 | |
| 0.2.0 | 2 / 4 | |
| 0.1.0 | 2 / 4 | |
| 0.0.1 | 2 / 4 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
2 findingsPackage 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 2021-03-10. This could indicate a legitimate maintainer transition or an account compromise.
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.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.