@cloud-ru/uikit-product-mobile-toaster
## Installation `npm i @cloud-ru/uikit-product-mobile-toaster`
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): Active UI component library; source growth reflects legitimate component additions, not injected payloads. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size growth consistent with UI library expansion; no obfuscation or suspicious patterns detected. | ai | |
| provenance | no-provenance | AI (provenance): Org-published UI kit; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.1.13 | 9 / 0 | |
| 1.1.12 | 9 / 0 | |
| 1.1.11 | 9 / 0 | |
| 1.1.10 | 9 / 0 | |
| 1.1.9 | 9 / 0 | |
| 1.1.5 | 9 / 0 | |
| 1.1.2 | 9 / 0 | |
| 0.1.36 | 9 / 0 | |
| 0.1.35 | 9 / 0 | |
| 0.1.34 | 9 / 0 | |
| 0.1.33 | 9 / 0 | |
| 0.1.32 | 9 / 0 | |
| 0.1.31 | 9 / 0 | |
| 0.1.30 | 9 / 0 | |
| 0.1.29 | 9 / 0 | |
| 0.1.28 | 9 / 0 | |
| 0.1.27 | 9 / 0 | |
| 0.1.26 | 9 / 0 |
v1.1.13
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.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
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.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.