@nivo/stream
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): @react-spring/web is a well-known, widely-used animation library; stable dependency for nivo packages. | ai | |
| dependencies | unvetted-dep:@nivo/axes | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai | |
| dependencies | unvetted-dep:@nivo/core | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai | |
| dependencies | unvetted-dep:@nivo/colors | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai | |
| dependencies | unvetted-dep:@nivo/scales | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai | |
| dependencies | unvetted-dep:@nivo/legends | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai | |
| dependencies | unvetted-dep:@nivo/tooltip | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component package; sparse README and no description are typical for nivo sub-packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with nivo monorepo sub-package publishing style. | ai | |
| phantom-deps | phantom-dep:@types/d3-shape | AI (phantom-deps): Type-only dependency used at build/compile time, not imported at runtime. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.99.0 | 10 / 0 | |
| 0.98.0 | 10 / 0 | |
| 0.97.0 | 10 / 0 | |
| 0.96.0 | 10 / 0 | |
| 0.95.0 | 10 / 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.