@alfalab/icons-logo
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:GazprombankSignCircleBoxMWhiteIcon.js | AI (source-diff): Same pattern: minified React SVG icon component with inline path data. Consistent with the package's icon library build output. | ai | |
| source-diff | obfuscated-file:EtprfSignBoxMColorIcon.js | AI (source-diff): Minified React SVG icon component; long lines are inline SVG path data, not obfuscation. Normal build output for this icon library. | ai | |
| source-diff | obfuscated-file:ArenzaMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:CheckofficeMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:CheckofficeMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:EnvyboxMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:EnvyboxMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:GetRadioMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:GetRadioMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:KonturDostupMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:KonturFocusMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:KonturFocusMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:KonturMarketMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:KonturMarketMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:PaypeopleMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:PaypeopleMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon libraries routinely add batches of new icon files; consistent with this package's history. | ai | |
| source-diff | obfuscated-file:KonturDostupMWhiteIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:ArenzaMColorIcon.js | AI (source-diff): Minified React SVG icon component; standard build output for this icon library. | ai | |
| source-diff | obfuscated-file:ClaudeSonnetSignBoxMIcon.js | AI (source-diff): Standard minified SVG icon bundle; long lines are SVG path data + React createElement, not obfuscation. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.57.0 | 0 / 0 | |
| 1.56.0 | 0 / 0 | |
| 1.55.0 | 0 / 0 | |
| 1.54.0 | 0 / 0 | |
| 1.53.0 | 0 / 0 | |
| 1.52.0 | 0 / 0 | |
| 1.51.0 | 0 / 0 | |
| 1.50.0 | 0 / 0 | |
| 1.49.0 | 0 / 0 | |
| 1.48.0 | 0 / 0 | |
| 1.47.0 | 0 / 0 | |
| 1.46.0 | 0 / 0 | |
| 1.45.0 | 0 / 0 | |
| 1.44.0 | 0 / 0 |
v1.57.0
3 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.55.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.54.0
18 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.
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.
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.
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.53.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.
v1.52.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.
v1.51.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.
v1.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.45.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.