@mozaic-ds/icons-svelte
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/custom-elements/assets/custom-element-CcZms_SI.js | AI (source-diff): Minified Svelte 5 runtime bundle from vite build, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/custom-elements/assets/client-kjZ7khFG.js | AI (source-diff): Vite-bundled Svelte runtime output, not obfuscation; matches custom-elements build. | ai | |
| source-diff | obfuscated-file:dist/custom-elements/assets/custom-element-DelEdaHx.js | AI (source-diff): Svelte 5 runtime bundled via vite build, not true obfuscation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-managed package; publisher has clean 60/0 approval history. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library; new files are icon assets, not injected code. | ai | |
| phantom-deps | phantom-dep:@mozaic-ds/icons | AI (phantom-deps): Same-org dependency used at build time via icons-builder; not directly imported in source but legitimately declared. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.7.2 | 2 / 11 | |
| 2.7.1 | 2 / 11 | |
| 2.7.0 | 2 / 11 | |
| 2.6.3 | 2 / 11 | |
| 2.6.1 | 2 / 10 | |
| 2.6.0 | 2 / 10 | |
| 2.5.0 | 2 / 10 | |
| 2.4.0 | 2 / 10 | |
| 2.3.1 | 2 / 10 | |
| 2.3.0 | 2 / 10 | |
| 2.2.0 | 2 / 10 | |
| 2.1.0 | 2 / 10 | |
| 2.0.0 | 2 / 10 |
v2.7.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.
v2.7.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.
v2.5.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.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.