@expo/styleguide-icons
Expo's icons for use on the web.
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:custom/ClaudeIcon.js | AI (source-diff): Minified generated icon component consistent with package's build pipeline, not malicious code. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Known maintainer per provenance info, manual publish by established Expo contributor. | ai | |
| source-diff | obfuscated-file:custom/PosthogIcon.js | AI (source-diff): esbuild-minified SVG icon component; no obfuscation or malicious payload, stable pattern for this icon library. | ai | |
| source-diff | obfuscated-file:custom/CodexIcon.js | AI (source-diff): esbuild-minified SVG icon component; no obfuscation or malicious payload, stable pattern for this icon library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library ships hundreds of individual SVG component files per build; large file count is expected and stable. | ai | |
| source-diff | obfuscated-file:solid/AirplaySolidIcon.mjs | AI (source-diff): esbuild-minified SVG icon component; no obfuscation or malicious payload, stable pattern for this icon library. | ai | |
| source-diff | obfuscated-file:custom/OpenaiIcon.js | AI (source-diff): esbuild-minified SVG icon component; no obfuscation or malicious payload, stable pattern for this icon library. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 4.2.8 | 1 / 5 | |
| 4.2.7 | 1 / 5 | |
| 4.2.6 | 1 / 5 | |
| 4.2.5 | 1 / 5 | |
| 4.2.4 | 1 / 5 | |
| 4.2.3 | 1 / 5 | |
| 4.2.2 | 1 / 5 | |
| 4.2.1 | 1 / 5 | |
| 4.2.0 | 1 / 8 | |
| 4.1.1 | 1 / 8 | |
| 4.1.0 | 1 / 8 | |
| 4.0.6 | 1 / 8 | |
| 4.0.5 | 1 / 8 | |
| 4.0.4 | 1 / 8 | |
| 4.0.3 | 1 / 8 | |
| 4.0.2 | 1 / 8 | |
| 4.0.1 | 1 / 8 | |
| 4.0.0 | 1 / 8 | |
| 3.0.1 | 1 / 8 | |
| 3.0.0 | 1 / 8 | |
| 2.3.4 | 1 / 8 | |
| 2.3.3 | 1 / 8 | |
| 2.3.2 | 1 / 8 | |
| 2.3.0 | 1 / 8 |
v4.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
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.
v4.0.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.
v4.0.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.
v4.0.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.
v3.0.1
3 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.
This version was published by a different npm account (alanhughes) than the most recent previously approved version (expo-bot) on 2026-03-02, but alanhughes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v3.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alanhughes) than the most recent previously approved version (expo-bot) on 2026-02-19, but alanhughes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (expo-bot) than the most recent previously approved version (kadikraman) on 2026-01-20, but expo-bot is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.