@gravity-ui/uikit
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package; no provenance is common and not a risk signal here. | ai | |
| dependencies | unvetted-dep:@gravity-ui/i18n | AI (dependencies): First-party Gravity UI dependency; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@gravity-ui/icons | AI (dependencies): First-party Gravity UI dependency; stable ecosystem package. | ai | |
| dependencies | unvetted-dep:@bem-react/classname | AI (dependencies): Well-known BEM utility; long-standing ecosystem package. | ai | |
| dependencies | unvetted-dep:@uiw/react-color | AI (dependencies): Popular React color picker library; no known malicious history. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 7.41.0 | 16 / 65 | |
| 7.40.0 | 16 / 65 | |
| 7.39.0 | 16 / 65 | |
| 7.38.0 | 16 / 65 | |
| 7.37.0 | 16 / 65 | |
| 7.36.1 | 16 / 65 | |
| 7.36.0 | 16 / 65 |
v7.41.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.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.
v7.36.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.36.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.