@cloud-ru/uikit-product-modal-predefined
## 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 — 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 | source-size-tripled | AI (source-diff): Growth consistent with expanding component library; no malicious indicators present. | ai | |
| source-diff | large-new-source-files | AI (source-diff): UI component library; large file additions reflect new modal variants, not injected code. | ai | |
| dependencies | unvetted-dep:@snack-uikit/fields | AI (dependencies): Sibling UI kit package from same org; consistent with monorepo pattern. | ai | |
| dependencies | unvetted-dep:@snack-uikit/carousel | AI (dependencies): Sibling UI kit package from same org; consistent with monorepo pattern. | ai | |
| dependencies | unvetted-dep:@snack-uikit/skeleton | AI (dependencies): Sibling UI kit package from same org; consistent with monorepo pattern. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-markdown | AI (dependencies): Internal cloud-ru monorepo package; consistent with org pattern. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-switch-row | AI (dependencies): Internal cloud-ru monorepo package; consistent with org pattern. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-toggles-predefined | AI (dependencies): Internal cloud-ru monorepo package; consistent with org pattern. | ai | |
| dependencies | unvetted-dep:@snack-uikit/pagination | AI (dependencies): Sibling UI kit package from same org; consistent with monorepo pattern. | ai | |
| dependencies | unvetted-dep:@snack-uikit/modal | AI (dependencies): Sibling UI kit package from same org; consistent with monorepo pattern. | ai | |
| provenance | no-provenance | AI (provenance): Established cloud-ru-tech org; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 2.2.5 | 17 / 0 | |
| 2.2.4 | 17 / 0 | |
| 2.2.3 | 17 / 0 | |
| 2.2.0 | 17 / 0 | |
| 2.1.4 | 17 / 0 | |
| 2.1.2 | 17 / 0 | |
| 2.0.4 | 17 / 0 | |
| 2.0.1 | 17 / 0 | |
| 0.9.16 | 17 / 0 | |
| 0.9.15 | 17 / 0 | |
| 0.9.12 | 17 / 0 | |
| 0.9.10 | 17 / 0 | |
| 0.9.9 | 17 / 0 | |
| 0.9.5 | 17 / 0 | |
| 0.9.4 | 17 / 0 | |
| 0.9.3 | 17 / 0 |
v2.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.