@infineon/infineon-icons
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:webfont | AI (phantom-deps): Build-time font generation tool; not imported at runtime, stable pattern for this icon package. | ai | |
| phantom-deps | phantom-dep:@xmldom/xmldom | AI (phantom-deps): SVG processing build dependency; referenced in config, not runtime import. | ai | |
| phantom-deps | phantom-dep:svgicons2svgfont | AI (phantom-deps): SVG-to-font build tool; referenced in config, not runtime import. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.8.1 | 3 / 8 | |
| 4.7.2 | 3 / 7 | |
| 4.7.1 | 3 / 7 | |
| 4.7.0 | 3 / 7 | |
| 4.4.1 | 3 / 7 | |
| 4.4.0 | 3 / 7 | |
| 4.2.0 | 3 / 7 | |
| 4.1.0 | 3 / 7 | |
| 4.0.0 | 3 / 7 |
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.