@nivo/voronoi
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/d3-scale | AI (phantom-deps): TypeScript type package declared as dep for consumers; not directly imported in source — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/d3-delaunay | AI (phantom-deps): TypeScript type package declared as dep for consumers; not directly imported in source — stable false positive for this package. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.99.0 | 7 / 0 | |
| 0.98.0 | 7 / 0 | |
| 0.97.0 | 7 / 0 | |
| 0.96.0 | 7 / 0 | |
| 0.95.0 | 7 / 0 | |
| 0.94.0 | 7 / 0 |
v0.99.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.96.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.