d3-arrays
DEPRECATED; renamed to d3-array (singular).
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 12+ years old with 13 versions and 4 approved dependents; 0.0.0 is a historical artifact, not a malicious indicator. | ai | |
| maintainer-change | maintainer-takeover | AI (maintainer-change): Transfer from jfsiii to mbostock (Mike Bostock, D3 creator) is a legitimate ownership transfer to the canonical D3 maintainer. Not a hijack. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change to mbostock is legitimate — he is the D3 creator and canonical owner of all d3-* packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mbostock added as maintainer is the expected outcome of D3 modularization; legitimate transfer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): jfsiii removal is part of the legitimate transfer to the canonical D3 org maintainer mbostock. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 0 / 5 | |
| 0.4.0 | 0 / 5 | |
| 0.3.1 | 0 / 5 | |
| 0.3.0 | 0 / 5 | |
| 0.2.0 | 0 / 5 | |
| 0.1.2 | 0 / 5 | |
| 0.1.1 | 0 / 5 | |
| 0.1.0 | 0 / 5 | |
| 0.0.4 | 0 / 5 | |
| 0.0.3 | 0 / 5 | |
| 0.0.2 | 0 / 5 | |
| 0.0.1 | 0 / 4 | |
| 0.0.0 | 0 / 3 |
v0.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
3 findingsAll previous maintainers (jfsiii) were replaced by new maintainers (mbostock). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2015-06-03. 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.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.