d3-hierarchy
Layout algorithms for visualizing hierarchical data.
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 Observable/D3 org account that took over maintenance of all D3 modules from mbostock — a well-documented, legitimate ecosystem transition. | ai | |
| provenance | no-provenance | AI (provenance): Published in 2020 before npm Sigstore provenance was available; absence is expected and not a risk signal for this package. | ai | |
| provenance | publisher-changed | AI (provenance): mbostock is the original D3 author returning as publisher; the change from recifs → mbostock is a legitimate transition back to the canonical maintainer, consistent with package.json author field and D3 project history. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 3.1.2 | 0 / 8 | |
| 3.1.1 | 0 / 8 | |
| 3.1.0 | 0 / 8 | |
| 3.0.1 | 0 / 8 | |
| 3.0.0 | 0 / 8 | |
| 2.0.0 | 0 / 8 | |
| 1.1.9 | 0 / 9 | |
| 1.1.8 | 0 / 9 | |
| 1.1.7 | 0 / 9 | |
| 1.1.6 | 0 / 10 | |
| 1.1.5 | 0 / 10 | |
| 1.1.4 | 0 / 7 | |
| 1.1.3 | 0 / 7 | |
| 1.1.2 | 0 / 7 | |
| 1.1.1 | 0 / 7 | |
| 1.1.0 | 0 / 7 | |
| 1.0.4 | 0 / 7 | |
| 1.0.3 | 0 / 7 | |
| 1.0.2 | 0 / 7 | |
| 1.0.1 | 0 / 7 | |
| 1.0.0 | 0 / 7 | |
| 0.3.0 | 0 / 7 | |
| 0.2.4 | 0 / 7 | |
| 0.2.3 | 0 / 7 | |
| 0.2.2 | 0 / 6 | |
| 0.2.1 | 0 / 6 | |
| 0.2.0 | 0 / 6 | |
| 0.1.0 | 0 / 6 | |
| 0.0.2 | 0 / 4 | |
| 0.0.1 | 0 / 4 |
v3.1.2
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
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-23. This could indicate a legitimate maintainer transition or an account compromise.