@versini/ui-icons
All the icons used in the UI-Components library.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package transitioned to GitHub Actions CI publishing; repo ownership unchanged under aversini org. | ai | |
| provenance | no-provenance | AI (provenance): Established package; missing provenance is CI/CD config, not a security defect. | ai | |
| dependencies | unvetted-dep:svgo | AI (dependencies): svgo is a well-known SVG optimizer; expected dependency for an icon package. | ai | |
| dependencies | unvetted-dep:@versini/ui-svgicon | AI (dependencies): First-party sibling package from the same publisher/org; stable pattern across versions. | ai | |
| phantom-deps | phantom-dep:svgo | AI (phantom-deps): svgo is used in build scripts (buildIcons.js), not imported at runtime; phantom-dep is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established icon library; sparse README/metadata is typical for component packages in a monorepo. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Icon library in a monorepo; missing description is cosmetic, not a risk signal. | ai |
Versions (showing 57 of 57)
| Version | Deps | Published |
|---|---|---|
| 4.29.1 | 0 / 3 | |
| 4.29.0 | 0 / 3 | |
| 4.28.0 | 0 / 3 | |
| 4.27.0 | 0 / 3 | |
| 4.26.5 | 0 / 3 | |
| 4.26.4 | 0 / 3 | |
| 4.26.3 | 0 / 3 | |
| 4.26.2 | 0 / 3 | |
| 4.26.1 | 0 / 3 | |
| 4.26.0 | 0 / 3 | |
| 4.25.0 | 0 / 3 | |
| 4.24.0 | 0 / 3 | |
| 4.23.1 | 0 / 3 | |
| 4.23.0 | 0 / 3 | |
| 4.22.2 | 0 / 3 | |
| 4.22.1 | 0 / 3 | |
| 4.22.0 | 0 / 3 | |
| 4.21.1 | 0 / 3 | |
| 4.21.0 | 0 / 3 | |
| 4.20.0 | 0 / 3 | |
| 4.19.2 | 0 / 3 | |
| 4.19.1 | 0 / 3 | |
| 4.19.0 | 0 / 3 | |
| 4.18.2 | 0 / 3 | |
| 4.18.1 | 0 / 3 | |
| 4.18.0 | 1 / 2 | |
| 4.17.0 | 1 / 2 | |
| 4.16.1 | 1 / 2 | |
| 4.16.0 | 1 / 2 | |
| 4.15.2 | 1 / 2 | |
| 4.15.1 | 1 / 2 | |
| 4.15.0 | 2 / 1 | |
| 4.13.0 | 2 / 1 | |
| 4.12.3 | 2 / 1 | |
| 4.12.2 | 2 / 1 | |
| 4.12.0 | 2 / 1 | |
| 4.11.0 | 2 / 1 | |
| 4.10.0 | 2 / 1 | |
| 4.9.0 | 2 / 1 | |
| 4.8.2 | 2 / 1 | |
| 4.8.1 | 2 / 1 | |
| 4.8.0 | 2 / 1 | |
| 4.7.0 | 2 / 2 | |
| 4.6.1 | 2 / 2 | |
| 4.6.0 | 2 / 2 | |
| 4.5.2 | 2 / 2 | |
| 4.5.1 | 2 / 2 | |
| 4.5.0 | 2 / 2 | |
| 4.4.3 | 1 / 1 | |
| 4.4.2 | 1 / 1 | |
| 4.4.1 | 1 / 1 | |
| 4.4.0 | 1 / 1 | |
| 4.3.0 | 1 / 1 | |
| 4.2.1 | 1 / 1 | |
| 4.2.0 | 2 / 0 | |
| 4.1.0 | 2 / 0 | |
| 4.0.0 | 2 / 0 |
v4.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.