@phosphor-icons/react
A clean and friendly icon family for React
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/index.cjs | AI (source-diff): dist/index.cjs is a standard Vite/Rollup minified CJS bundle for a large React icon library. Minification is expected; no malicious patterns present. | ai | |
| source-diff | obfuscated-file:dist/index.cjs | AI (source-diff): dist/index.cjs is a standard Vite-built minified bundle for a React icon library. Long lines are SVG path data for hundreds of icons, not malicious obfuscation. Stable pattern for this package. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Phosphor Icons is a large icon library; new versions routinely add hundreds of new icon source files. Large file counts are expected and benign for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.1.10 | 0 / 15 | |
| 2.1.9 | 0 / 15 | |
| 2.1.8 | 0 / 15 | |
| 2.1.7 | 0 / 14 | |
| 2.1.6 | 0 / 14 | |
| 2.1.5 | 0 / 14 | |
| 2.1.4 | 0 / 14 | |
| 2.1.3 | 0 / 13 | |
| 2.1.2 | 0 / 13 | |
| 2.1.1 | 0 / 13 | |
| 2.1.0 | 0 / 13 | |
| 2.0.15 | 0 / 13 | |
| 2.0.14 | 0 / 13 | |
| 2.0.13 | 0 / 13 | |
| 2.0.12 | 0 / 13 | |
| 2.0.11 | 0 / 13 | |
| 2.0.10 | 0 / 13 | |
| 2.0.9 | 0 / 13 | |
| 2.0.8 | 0 / 13 | |
| 2.0.7 | 0 / 13 | |
| 2.0.6 | 0 / 13 | |
| 2.0.5 | 0 / 13 | |
| 2.0.4 | 0 / 13 | |
| 2.0.3 | 0 / 13 | |
| 2.0.2 | 0 / 13 | |
| 2.0.1 | 0 / 13 | |
| 2.0.0 | 0 / 13 |
v2.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
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.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.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.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.