d3-force
Force-directed graph layout using velocity Verlet integration.
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 recognized Observable/D3 team npm account; this is a documented legitimate maintainer transition for the d3 ecosystem, not a takeover. | ai | |
| provenance | no-provenance | AI (provenance): d3-force is a long-established D3 package; lack of Sigstore provenance is a process gap, not a security risk for this well-known package. | ai | |
| provenance | publisher-changed | AI (provenance): mbostock is the original author of d3-force and the D3 ecosystem; the change from recifs back to mbostock is a legitimate return to the original maintainer, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by a major version bump (2.x → 3.0.0) is normal for mature, stable libraries. No other risk signals present. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 3 / 4 | |
| 2.1.1 | 3 / 4 | |
| 2.1.0 | 3 / 4 | |
| 2.0.1 | 3 / 4 | |
| 2.0.0 | 3 / 4 | |
| 1.2.1 | 4 / 4 | |
| 1.2.0 | 4 / 4 | |
| 1.1.2 | 4 / 4 | |
| 1.1.1 | 4 / 4 | |
| 1.1.0 | 4 / 5 | |
| 1.0.6 | 4 / 5 | |
| 1.0.5 | 4 / 5 | |
| 1.0.4 | 4 / 5 | |
| 1.0.3 | 4 / 5 | |
| 1.0.2 | 4 / 5 | |
| 1.0.1 | 4 / 5 | |
| 1.0.0 | 4 / 5 | |
| 0.7.1 | 4 / 5 | |
| 0.7.0 | 4 / 5 | |
| 0.6.3 | 4 / 5 | |
| 0.6.2 | 4 / 4 | |
| 0.6.1 | 4 / 4 | |
| 0.6.0 | 4 / 4 | |
| 0.5.0 | 4 / 4 | |
| 0.4.1 | 4 / 4 | |
| 0.4.0 | 4 / 4 | |
| 0.3.0 | 4 / 4 | |
| 0.2.2 | 4 / 4 | |
| 0.2.1 | 4 / 4 | |
| 0.2.0 | 4 / 4 | |
| 0.1.0 | 4 / 4 | |
| 0.0.4 | 4 / 4 | |
| 0.0.3 | 4 / 4 | |
| 0.0.2 | 4 / 4 | |
| 0.0.1 | 4 / 4 |
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2021-06-05. 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.1.1
2 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.
v2.1.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.
[Accepted risk] 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.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.