@lobehub/icons
Popular AI / LLM Model Brand SVG Logo and Icon Collection
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:es/SillyTavern/components/Mono.js | AI (source-diff): Babel-transpiled React component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:es/AirJelly/components/Text.js | AI (source-diff): Babel-transpiled React component; standard build output for this icon library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds new icon sets; 108 files is normal for new brand additions. | ai | |
| source-diff | obfuscated-file:es/SillyTavern/components/Color.js | AI (source-diff): Babel-transpiled React component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:es/WorldRouter/components/Mono.js | AI (source-diff): Babel-transpiled React component; standard build output for this icon library. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): URLs in this package are brand/docs metadata for AI service icons, not C2 links; stable false positive for this icon library. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @lobehub/icons package; Levenshtein match to 'cors' is a heuristic false positive with no real similarity. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.10.0 | 4 / 45 | |
| 5.9.0 | 4 / 45 | |
| 5.8.0 | 4 / 45 | |
| 5.7.0 | 4 / 45 | |
| 5.6.0 | 4 / 45 | |
| 5.5.4 | 4 / 45 | |
| 5.5.3 | 4 / 45 | |
| 5.5.2 | 4 / 45 | |
| 5.5.1 | 4 / 45 | |
| 5.5.0 | 4 / 45 | |
| 5.4.0 | 4 / 45 | |
| 5.3.1 | 3 / 46 | |
| 5.3.0 | 3 / 46 |
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
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.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.