@nivo/colors
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @nivo package in a well-known monorepo; edit-distance match to 'cors' is coincidental. | ai | |
| phantom-deps | phantom-dep:@nivo/core | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for intra-monorepo deps. | ai | |
| phantom-deps | phantom-dep:@types/d3-color | AI (phantom-deps): TypeScript type package; not directly imported but used at compile time. | ai | |
| phantom-deps | phantom-dep:@types/d3-scale | AI (phantom-deps): TypeScript type package; not directly imported but used at compile time. | ai | |
| phantom-deps | phantom-dep:@types/d3-scale-chromatic | AI (phantom-deps): TypeScript type package; not directly imported but used at compile time. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.99.0 | 9 / 0 | |
| 0.98.0 | 9 / 0 | |
| 0.97.0 | 9 / 0 | |
| 0.96.0 | 9 / 0 | |
| 0.95.0 | 9 / 0 | |
| 0.94.0 | 9 / 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.94.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.