@cloud-ru/uikit-product-icons
## Installation
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:dist/cjs/components/flag-icons/Afghanistan.js | AI (source-diff): Long lines are SVG path data in compiled TypeScript output, not obfuscation. Stable pattern for this icon library. | ai | |
| source-diff | obfuscated-file:dist/esm/components/flag-icons/Afghanistan.js | AI (source-diff): Same as CJS counterpart — SVG path data in compiled ESM output, not obfuscation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Icon library adding flag/logo icon sets; large file counts are expected for this package type. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase reflects new icon categories (flags, logos, sprites); consistent with package purpose. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common; no other risk signals present for this package. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 17.5.1 | 2 / 12 | |
| 17.5.0 | 2 / 12 | |
| 17.4.0 | 2 / 12 | |
| 17.3.0 | 2 / 12 | |
| 17.2.0 | 2 / 12 | |
| 17.1.1 | 2 / 12 | |
| 17.1.0 | 2 / 12 | |
| 17.0.6 | 2 / 12 | |
| 17.0.5 | 2 / 12 | |
| 17.0.4 | 2 / 12 | |
| 17.0.3 | 2 / 12 | |
| 17.0.2 | 2 / 12 | |
| 17.0.1 | 2 / 12 | |
| 17.0.0 | 2 / 12 | |
| 16.2.0 | 2 / 13 | |
| 16.1.1 | 2 / 13 | |
| 16.1.0 | 2 / 13 | |
| 16.0.1 | 2 / 13 | |
| 16.0.0 | 2 / 13 | |
| 15.1.6 | 2 / 13 | |
| 15.1.5 | 2 / 13 | |
| 15.1.4 | 2 / 13 | |
| 15.1.3 | 2 / 13 | |
| 15.1.2 | 2 / 13 | |
| 15.1.1 | 2 / 13 |
v17.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v16.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v15.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.