@bigbinary/neeto-icons
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/misc/DodoPaymentsTypeface.js | AI (source-diff): Long single-line minified SVG icon component, matches package's icon-library purpose. | ai | |
| source-diff | obfuscated-file:dist/cjs/misc/DodoPaymentsTypeface.js | AI (source-diff): CJS build of same icon component, same benign minification. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Icon libraries often batch-add new logos infrequently; publisher has strong track record. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.20.88 | 0 / 34 | |
| 1.20.87 | 0 / 34 | |
| 1.20.86 | 0 / 34 | |
| 1.20.85 | 0 / 34 | |
| 1.20.84 | 0 / 33 | |
| 1.20.83 | 0 / 33 | |
| 1.20.82 | 0 / 34 | |
| 1.20.81 | 0 / 34 | |
| 1.20.80 | 0 / 34 | |
| 1.20.79 | 0 / 34 | |
| 1.20.78 | 0 / 34 | |
| 1.20.77 | 0 / 33 | |
| 1.20.76 | 0 / 33 | |
| 1.20.75 | 0 / 33 | |
| 1.20.74 | 0 / 33 | |
| 1.20.73 | 0 / 33 | |
| 1.20.72 | 0 / 33 | |
| 1.20.71 | 0 / 33 | |
| 1.20.70 | 0 / 33 | |
| 1.20.68 | 0 / 33 |
v1.20.87
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v1.20.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.