@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/nivo-colors.mjs | AI (source-diff): Minified ESM build output with clear import graph; not obfuscation. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established 1.5M-dl package; README/keyword heuristics are false positives. | ai | |
| phantom-deps | phantom-dep:@types/prop-types | AI (phantom-deps): Framework-scoped @types package, loaded by convention. | ai | |
| phantom-deps | phantom-dep:@types/d3-scale | AI (phantom-deps): TypeScript type package; not directly imported but used at compile time. | ai | |
| 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:@types/d3-scale-chromatic | AI (phantom-deps): TypeScript type package; not directly imported but used at compile time. | 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 |
Versions (showing 15 of 15)
| 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 | |
| 0.93.0 | 9 / 0 | |
| 0.92.2 | 9 / 0 | |
| 0.92.0 | 9 / 0 | |
| 0.91.0 | 8 / 0 | |
| 0.90.0 | 8 / 0 | |
| 0.89.1 | 8 / 0 | |
| 0.89.0 | 10 / 0 | |
| 0.88.0 | 10 / 0 | |
| 0.87.0 | 10 / 0 |
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.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. Consider requesting the maintainer enable provenance via CI/CD.
v0.87.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.