@cloud-ru/uikit-product-page-layout
## Installation `npm i @cloud-ru/uikit-product-page-layout`
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@snack-uikit/list | AI (dependencies): @snack-uikit/list is a sibling UI kit dep consistent with all other @snack-uikit/* deps in this package; stable pattern. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Size growth attributable to adding three new snack-uikit component dependencies; consistent with legitimate feature expansion. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Tripling explained by bundled dist output from three newly added UI component deps; no obfuscation or payload indicators. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this org's packages; not a security signal here. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.1.8 | 17 / 0 | |
| 2.1.7 | 17 / 0 | |
| 2.1.6 | 17 / 0 | |
| 2.1.4 | 17 / 0 | |
| 2.1.3 | 17 / 0 | |
| 2.1.2 | 17 / 0 | |
| 2.1.0 | 17 / 0 | |
| 2.0.10 | 17 / 0 | |
| 2.0.8 | 17 / 0 | |
| 2.0.2 | 17 / 0 | |
| 2.0.1 | 17 / 0 | |
| 0.23.3 | 17 / 0 | |
| 0.23.1 | 17 / 0 | |
| 0.23.0 | 17 / 0 | |
| 0.22.5 | 17 / 0 | |
| 0.22.4 | 17 / 0 | |
| 0.22.3 | 17 / 0 | |
| 0.22.2 | 17 / 0 | |
| 0.22.1 | 17 / 0 | |
| 0.22.0 | 17 / 0 | |
| 0.21.6 | 14 / 0 | |
| 0.21.5 | 14 / 0 | |
| 0.21.4 | 14 / 0 | |
| 0.21.3 | 14 / 0 |
v2.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.6
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.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
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.23.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.