@alfalab/icons
Design System UI 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, 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:flag/dist/AbkhaziaMColorIcon.js | AI (source-diff): Minified bundled icon component, not true obfuscation; expected for icon library dist files. | ai | |
| source-diff | obfuscated-file:logotype/dist/TinkoffBankMColorIcon.js | AI (source-diff): Minified bundled SVG icon component, not true obfuscation. | ai | |
| source-diff | obfuscated-file:logotype/dist/SberBankMColorIcon.js | AI (source-diff): Minified bundled SVG icon component, not true obfuscation. | ai | |
| source-diff | obfuscated-file:logo/dist/EtprfSignBoxMColorIcon.js | AI (source-diff): Minified generated icon component, not obfuscation; matches package's icon-generation purpose. | ai | |
| source-diff | obfuscated-file:logo/dist/GazprombankSignCircleBoxMWhiteIcon.js | AI (source-diff): Minified generated icon component, not obfuscation; matches package's icon-generation purpose. | ai | |
| source-diff | obfuscated-file:logotype/dist/GosuslugiMColorIcon.js | AI (source-diff): Minified icon-component build output, not true obfuscation. | ai | |
| source-diff | obfuscated-file:logotype/dist/GosuslugiXlColorIcon.js | AI (source-diff): Minified icon-component build output, not true obfuscation; matches package's stated function. | ai | |
| source-diff | obfuscated-file:ios/dist/TouchIdXxlIcon.js | AI (source-diff): Minified icon-component build output, not true obfuscation. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stale change from 2022, unremoved for years; not indicative of takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org migration to core-ds-bot, stable and long-lived publisher account. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org migration, old maintainers rotated out long ago. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Icon set expansions routinely cause dramatic size increases in this package; consistent with new logo icons added. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library regularly adds large batches of new icon files; size growth matches new icon additions. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @alfalab/icons package is a legitimate design-system icon library, not a typo of cors. | ai |
Versions (showing 41 of 141)
| Version | Deps | Published |
|---|---|---|
| 3.63.0 | 0 / 36 | |
| 3.62.0 | 0 / 36 | |
| 3.61.0 | 0 / 36 | |
| 3.60.0 | 0 / 36 | |
| 3.59.0 | 0 / 36 | |
| 3.58.0 | 0 / 36 | |
| 3.57.0 | 0 / 36 | |
| 3.56.0 | 0 / 36 | |
| 3.55.0 | 0 / 36 | |
| 3.54.0 | 0 / 36 | |
| 3.53.0 | 0 / 36 | |
| 3.52.0 | 0 / 36 | |
| 3.51.0 | 0 / 36 | |
| 3.50.0 | 0 / 36 | |
| 3.49.0 | 0 / 36 | |
| 3.48.0 | 0 / 36 | |
| 3.47.0 | 0 / 36 | |
| 3.46.0 | 0 / 36 | |
| 3.45.0 | 0 / 36 | |
| 3.44.0 | 0 / 36 | |
| 3.43.0 | 0 / 36 | |
| 3.28.0 | 0 / 36 | |
| 3.27.0 | 0 / 36 | |
| 3.18.0 | 0 / 36 | |
| 3.17.0 | 0 / 36 | |
| 3.16.0 | 0 / 36 | |
| 3.15.0 | 0 / 36 | |
| 3.14.0 | 0 / 36 | |
| 3.13.0 | 0 / 36 | |
| 3.12.0 | 0 / 36 | |
| 3.11.0 | 0 / 36 | |
| 3.10.0 | 0 / 36 | |
| 3.9.0 | 0 / 36 | |
| 3.8.0 | 0 / 36 | |
| 3.7.0 | 0 / 36 | |
| 3.6.0 | 0 / 36 | |
| 3.5.0 | 0 / 36 | |
| 3.4.0 | 0 / 36 | |
| 3.3.0 | 0 / 36 | |
| 3.2.0 | 0 / 36 | |
| 3.1.0 | 0 / 36 |
v3.63.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-22. It has since remained available on npm for 1463 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.62.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-21. It has since remained available on npm for 1464 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.61.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
This version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-20. It has since remained available on npm for 1465 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.60.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-20. It has since remained available on npm for 1465 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.59.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-18. It has since remained available on npm for 1467 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.58.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-13. It has since remained available on npm for 1472 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.57.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-11. It has since remained available on npm for 1474 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.56.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-06. It has since remained available on npm for 1479 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.55.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-04. It has since remained available on npm for 1481 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.54.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-07-04. It has since remained available on npm for 1481 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.53.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-30. It has since remained available on npm for 1485 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.52.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-29. It has since remained available on npm for 1486 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.51.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-28. It has since remained available on npm for 1487 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.50.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-24. It has since remained available on npm for 1491 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.49.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-22. It has since remained available on npm for 1493 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.48.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-17. It has since remained available on npm for 1498 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.47.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-17. It has since remained available on npm for 1498 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.46.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-16. It has since remained available on npm for 1499 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.45.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-16. It has since remained available on npm for 1499 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.44.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-15. It has since remained available on npm for 1500 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.43.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-06-08. It has since remained available on npm for 1507 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.28.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-04-29. It has since remained available on npm for 1547 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
2 findingsThis version was published by a different npm account (core-ds-bot) than the most recent previously approved version (dmitrsavk) on 2022-04-25. It has since remained available on npm for 1551 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.