three-forcegraph
Force-directed graph as a ThreeJS 3d object
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 | no-provenance | AI (provenance): Mature package with long history; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.43.4 | 10 / 11 | |
| 1.43.3 | 10 / 11 | |
| 1.43.2 | 10 / 11 | |
| 1.43.1 | 10 / 11 | |
| 1.43.0 | 10 / 11 |
v1.43.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.43.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.