d3-quadtree
Two-dimensional recursive spatial subdivision.
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 org account that took over all d3-* packages from mbostock in 2020; this is a well-documented legitimate org-level transition, not a suspicious takeover. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is consistent with the publish environment change during the 2020 D3 org transition; no security implication for this package. | ai | |
| provenance | publisher-changed | AI (provenance): mbostock is the original d3 author and package.json author; the transition from recifs back to mbostock is a legitimate maintainer return, not a compromise. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.0.1 | 0 / 5 | |
| 3.0.0 | 0 / 5 | |
| 2.0.0 | 0 / 5 | |
| 1.0.7 | 0 / 5 | |
| 1.0.6 | 0 / 5 | |
| 1.0.5 | 0 / 5 | |
| 1.0.4 | 0 / 5 | |
| 1.0.3 | 0 / 6 | |
| 1.0.2 | 0 / 6 | |
| 1.0.1 | 0 / 6 | |
| 1.0.0 | 0 / 6 | |
| 0.8.0 | 0 / 6 | |
| 0.7.3 | 0 / 6 | |
| 0.7.2 | 0 / 5 | |
| 0.7.1 | 0 / 5 | |
| 0.7.0 | 0 / 5 | |
| 0.6.0 | 0 / 5 | |
| 0.5.0 | 0 / 5 | |
| 0.4.0 | 0 / 5 | |
| 0.3.0 | 0 / 5 | |
| 0.2.1 | 0 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.1.1 | 0 / 5 | |
| 0.1.0 | 0 / 5 | |
| 0.0.3 | 0 / 5 | |
| 0.0.2 | 0 / 5 | |
| 0.0.1 | 0 / 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.
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.