@cloud-ru/uikit-product-mobile-info-row
## Installation `npm i @cloud-ru/uikit-product-mobile-info-row`
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 library ships src/ files; growth in source count reflects feature additions, not injection. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth aligns with new component source files; no obfuscation or suspicious payloads indicated. | ai | |
| dependencies | unvetted-dep:@snack-uikit/skeleton | AI (dependencies): Legitimate UI library dependency from snack-uikit ecosystem; no malicious indicators. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-info-row | AI (dependencies): First-party sibling package from same cloud-ru-tech org; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common for this publisher's UI component packages; not a risk signal here. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.1.14 | 8 / 0 | |
| 1.1.13 | 8 / 0 | |
| 1.1.12 | 8 / 0 | |
| 1.1.11 | 8 / 0 | |
| 1.1.10 | 8 / 0 | |
| 1.1.9 | 8 / 0 | |
| 1.1.8 | 8 / 0 | |
| 1.1.7 | 8 / 0 | |
| 1.1.6 | 8 / 0 | |
| 1.1.5 | 8 / 0 | |
| 1.1.4 | 8 / 0 | |
| 1.1.3 | 8 / 0 | |
| 1.1.2 | 8 / 0 | |
| 1.1.1 | 8 / 0 | |
| 1.1.0 | 8 / 0 | |
| 0.6.32 | 8 / 0 | |
| 0.6.31 | 8 / 0 | |
| 0.6.30 | 8 / 0 | |
| 0.6.29 | 8 / 0 | |
| 0.6.28 | 8 / 0 | |
| 0.6.27 | 8 / 0 | |
| 0.6.26 | 8 / 0 | |
| 0.6.25 | 8 / 0 | |
| 0.6.24 | 8 / 0 | |
| 0.6.23 | 8 / 0 | |
| 0.6.22 | 8 / 0 | |
| 0.6.21 | 8 / 0 | |
| 0.6.20 | 8 / 0 |
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
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.1.10
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.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.