@nivo/bump
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nivo/axes | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@nivo/core | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@nivo/text | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@nivo/colors | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@nivo/scales | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@nivo/legends | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@nivo/tooltip | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@nivo/voronoi | AI (dependencies): Same-monorepo sibling dep; always released in lockstep with this package. | ai | |
| dependencies | unvetted-dep:@react-spring/web | AI (dependencies): Well-known animation library; standard dep for nivo packages. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): @nivo/bump is a scoped package in the established nivo dataviz org; Levenshtein match to 'yup' is a false positive. | ai | |
| phantom-deps | phantom-dep:@nivo/legends | AI (phantom-deps): Same-org scoped dep; phantom-dep heuristic unreliable for monorepo packages. | ai | |
| phantom-deps | phantom-dep:@types/d3-scale | AI (phantom-deps): @types packages are type-only and not directly imported at runtime; false positive. | ai | |
| phantom-deps | phantom-dep:@types/d3-shape | AI (phantom-deps): @types packages are type-only and not directly imported at runtime; false positive. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.99.0 | 14 / 0 | |
| 0.98.0 | 14 / 0 | |
| 0.97.0 | 14 / 0 | |
| 0.96.0 | 14 / 0 | |
| 0.95.0 | 14 / 0 | |
| 0.94.0 | 14 / 0 | |
| 0.93.0 | 14 / 0 | |
| 0.92.2 | 14 / 0 | |
| 0.92.1 | 14 / 0 | |
| 0.92.0 | 14 / 0 | |
| 0.91.0 | 12 / 0 | |
| 0.90.0 | 12 / 0 | |
| 0.89.1 | 12 / 0 | |
| 0.89.0 | 12 / 0 | |
| 0.88.0 | 12 / 0 | |
| 0.87.0 | 12 / 0 |
v0.94.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.91.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.90.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.88.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.