@cloud-ru/uikit-product-mobile-table
## Installation `npm i @cloud-ru/uikit-product-mobile-table`
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): Part of the snack-uikit component family used throughout this package's ecosystem; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@snack-uikit/table | AI (dependencies): Core table dependency for a mobile-table package; expected and consistent with package purpose. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all cloud-ru-tech packages; no provenance is the norm for this publisher. | ai | |
| phantom-deps | phantom-dep:@snack-uikit/figma-tokens | AI (phantom-deps): Design token package referenced in config/build files only; not a runtime import concern for a UI component library. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.2.14 | 24 / 1 | |
| 2.2.13 | 24 / 1 | |
| 2.2.11 | 24 / 1 | |
| 2.2.10 | 24 / 1 | |
| 2.2.3 | 24 / 1 | |
| 0.17.0 | 23 / 1 | |
| 0.13.1 | 17 / 1 | |
| 0.11.4 | 17 / 1 | |
| 0.11.3 | 17 / 1 |
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.