@fuxishi/svg-icon
Vue 3 图标组件,支持 Iconify 图标集和本地 SVG
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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/antdv-CAtYGYXt.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/element-plus-DC2P6hNA.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/naive-s_wck2Gs.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/tdesign-BSffwuGT.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/useIconSelect-itguTehi.cjs | AI (source-diff): Standard Vite/Rollup minified Vue composable output; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/antdv-D2KbEiGr.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/element-plus-GI8Raxvy.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/naive-Dael8tcl.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component bundle; no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/tdesign-C0QbfBd4.cjs | AI (source-diff): Standard Vite/Rollup minified Vue component bundle; no malicious patterns. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.0.7 | 1 / 5 | |
| 1.0.6 | 1 / 12 | |
| 1.0.5 | 1 / 12 | |
| 1.0.4 | 1 / 12 | |
| 1.0.3 | 1 / 12 | |
| 1.0.2 | 1 / 12 | |
| 1.0.1 | 1 / 12 | |
| 1.0.0 | 1 / 12 | |
| 0.1.1 | 1 / 12 | |
| 0.1.0 | 1 / 12 |
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
6 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.
Newly 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.
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.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
5 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.
Newly 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.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.