@cloud-ru/uikit-product-calculator
## Installation
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/pagination | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| dependencies | unvetted-dep:@snack-uikit/tag | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| dependencies | unvetted-dep:@snack-uikit/card | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| dependencies | unvetted-dep:@snack-uikit/link | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| dependencies | unvetted-dep:@snack-uikit/list | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| dependencies | unvetted-dep:@snack-uikit/modal | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| dependencies | unvetted-dep:@snack-uikit/fields | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| dependencies | unvetted-dep:@snack-uikit/carousel | AI (dependencies): Established @snack-uikit UI library component; consistent with rest of dep tree. | ai | |
| provenance | no-provenance | AI (provenance): Established org package; lack of Sigstore provenance is common and not a risk signal here. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 1.9.6 | 31 / 1 | |
| 1.9.5 | 31 / 1 | |
| 1.9.4 | 31 / 1 | |
| 1.9.3 | 31 / 1 | |
| 1.9.2 | 31 / 1 | |
| 1.9.1 | 31 / 1 | |
| 1.9.0 | 31 / 1 | |
| 1.8.1 | 31 / 1 | |
| 1.8.0 | 31 / 1 | |
| 1.7.0 | 31 / 1 | |
| 1.6.1 | 31 / 1 | |
| 1.6.0 | 31 / 1 | |
| 1.5.4 | 31 / 1 | |
| 1.5.3 | 31 / 1 | |
| 1.5.2 | 31 / 1 | |
| 1.5.1 | 31 / 1 | |
| 1.5.0 | 31 / 1 | |
| 1.4.5 | 31 / 1 | |
| 1.4.4 | 31 / 1 | |
| 1.4.3 | 31 / 1 | |
| 1.4.2 | 31 / 1 | |
| 1.4.1 | 31 / 1 | |
| 1.4.0 | 31 / 1 | |
| 1.3.2 | 31 / 1 | |
| 1.3.1 | 31 / 1 | |
| 1.3.0 | 31 / 1 | |
| 1.2.2 | 31 / 1 | |
| 1.2.1 | 31 / 1 | |
| 1.2.0 | 31 / 1 | |
| 1.1.6 | 31 / 1 | |
| 1.1.5 | 31 / 1 | |
| 1.1.4 | 31 / 1 | |
| 1.1.3 | 31 / 1 | |
| 1.1.2 | 31 / 1 | |
| 1.1.1 | 31 / 1 | |
| 1.1.0 | 31 / 1 | |
| 0.40.2 | 31 / 1 | |
| 0.40.1 | 31 / 1 | |
| 0.40.0 | 31 / 1 | |
| 0.39.0 | 31 / 1 | |
| 0.38.1 | 31 / 1 | |
| 0.38.0 | 31 / 1 | |
| 0.37.0 | 31 / 1 | |
| 0.36.1 | 31 / 1 | |
| 0.36.0 | 31 / 1 | |
| 0.35.7 | 31 / 1 | |
| 0.35.6 | 31 / 1 | |
| 0.35.5 | 31 / 1 | |
| 0.35.4 | 31 / 1 | |
| 0.35.3 | 31 / 1 | |
| 0.35.2 | 31 / 1 |
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.40.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
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.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.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.38.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.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.36.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.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.35.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.3
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.35.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.