@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, 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/nivo-stream.mjs | AI (source-diff): Bundled/minified build output, not obfuscation; standard esbuild-style single-line dist file. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an official @nivo sibling package from the same monorepo. | ai | |
| 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/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 | |
| dependencies | unvetted-dep:@nivo/core | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai | |
| dependencies | unvetted-dep:@nivo/axes | AI (dependencies): Sibling monorepo package; always released in lockstep with @nivo/stream. | ai |
Versions (showing 16 of 16)
| 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 | |
| 0.94.0 | 10 / 0 | |
| 0.93.0 | 10 / 0 | |
| 0.92.2 | 10 / 0 | |
| 0.92.1 | 10 / 0 | |
| 0.92.0 | 10 / 0 | |
| 0.91.0 | 9 / 0 | |
| 0.90.0 | 9 / 0 | |
| 0.89.1 | 9 / 0 | |
| 0.89.0 | 9 / 0 | |
| 0.88.0 | 9 / 0 | |
| 0.87.0 | 9 / 0 |
v0.94.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.93.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.92.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.91.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.90.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.89.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.