@nivo/sunburst
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-sunburst.mjs | AI (source-diff): Minified bundler output for the published dist entry; stable across versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-package; sparse README and no description are typical for nivo component packages. | ai | |
| dependencies | unvetted-dep:@nivo/core | AI (dependencies): Sibling nivo monorepo package; expected dependency pattern across all nivo versions. | ai | |
| dependencies | unvetted-dep:@nivo/colors | AI (dependencies): Sibling nivo monorepo package; expected dependency pattern across all nivo versions. | ai | |
| dependencies | unvetted-dep:@nivo/tooltip | AI (dependencies): Sibling nivo monorepo package; expected dependency pattern across all nivo versions. | ai | |
| phantom-deps | phantom-dep:@types/d3-hierarchy | AI (phantom-deps): @types packages are type-only and conventionally declared as runtime deps in nivo packages; stable false positive. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.99.0 | 8 / 0 | |
| 0.98.0 | 8 / 0 | |
| 0.97.0 | 8 / 0 | |
| 0.96.0 | 8 / 0 | |
| 0.95.0 | 8 / 0 | |
| 0.94.0 | 8 / 0 | |
| 0.93.0 | 8 / 0 | |
| 0.92.2 | 8 / 0 | |
| 0.92.1 | 8 / 0 | |
| 0.92.0 | 8 / 0 | |
| 0.91.0 | 7 / 0 | |
| 0.90.0 | 7 / 0 | |
| 0.89.1 | 7 / 0 | |
| 0.89.0 | 7 / 0 | |
| 0.88.0 | 7 / 0 |
v0.96.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.95.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.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.