@cloud-ru/uikit-product-utils
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:@sbercloud/figma-tokens-web | AI (dependencies): Optional design-token dep from same org; stable false positive for this UI kit package. | ai | |
| dependencies | unvetted-dep:@sbercloud/figma-tokens-admin | AI (dependencies): Optional design-token dep from same org; stable false positive for this UI kit package. | ai | |
| dependencies | unvetted-dep:@sbercloud/figma-tokens-giga-id | AI (dependencies): Optional design-token dep from same org; stable false positive for this UI kit package. | ai | |
| dependencies | unvetted-dep:@sbercloud/figma-tokens-mlspace | AI (dependencies): Optional design-token dep from same org; stable false positive for this UI kit package. | ai | |
| dependencies | unvetted-dep:@sbercloud/figma-tokens-cloud-platform | AI (dependencies): Optional design-token dep from same org; stable false positive for this UI kit package. | ai | |
| provenance | no-provenance | AI (provenance): Org does not use Sigstore attestation; consistent across all versions, not a risk indicator for this package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 9.1.0 | 5 / 3 | |
| 9.0.2 | 3 / 1 | |
| 9.0.1 | 3 / 1 | |
| 9.0.0 | 3 / 1 | |
| 8.1.0 | 3 / 1 | |
| 8.0.2 | 3 / 1 | |
| 8.0.1 | 3 / 1 | |
| 8.0.0 | 3 / 1 | |
| 7.0.3 | 3 / 1 | |
| 7.0.2 | 3 / 1 | |
| 7.0.1 | 8 / 1 | |
| 7.0.0 | 8 / 1 |
v9.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.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.
v7.0.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.