@cloud-ru/uikit-product-site-csat
Site csat form
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 | large-new-source-files | AI (source-diff): UI component package ships src/ in files array; new source files reflect legitimate feature growth. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth matches dual ESM/CJS build output plus included src files; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@snack-uikit/chips | AI (dependencies): Part of the same Cloud.ru/Sber snack-uikit ecosystem; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@snack-uikit/fields | AI (dependencies): Part of the same Cloud.ru/Sber snack-uikit ecosystem; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@snack-uikit/popover | AI (dependencies): Part of the same Cloud.ru/Sber snack-uikit ecosystem; consistent with package purpose. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals present for this package. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.2.10 | 12 / 0 | |
| 1.2.9 | 12 / 0 | |
| 1.2.8 | 12 / 0 | |
| 1.2.7 | 12 / 0 | |
| 1.2.6 | 12 / 0 | |
| 1.2.5 | 12 / 0 | |
| 1.2.4 | 12 / 0 | |
| 1.2.3 | 12 / 0 | |
| 1.2.2 | 12 / 0 | |
| 1.2.1 | 12 / 0 | |
| 1.2.0 | 12 / 0 | |
| 1.1.6 | 12 / 0 | |
| 1.1.5 | 12 / 0 | |
| 1.1.4 | 12 / 0 | |
| 1.1.3 | 12 / 0 | |
| 1.1.2 | 12 / 0 | |
| 1.1.1 | 12 / 0 | |
| 1.1.0 | 12 / 0 | |
| 0.2.8 | 12 / 1 | |
| 0.2.7 | 12 / 1 | |
| 0.2.6 | 12 / 1 | |
| 0.2.5 | 12 / 1 | |
| 0.2.4 | 12 / 1 | |
| 0.2.3 | 12 / 1 | |
| 0.2.2 | 12 / 1 | |
| 0.2.1 | 12 / 1 | |
| 0.2.0 | 12 / 1 | |
| 0.1.18 | 12 / 1 | |
| 0.1.17 | 12 / 1 | |
| 0.1.16 | 12 / 1 | |
| 0.1.15 | 12 / 1 |
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
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.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.