@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, so a manually published version cannot be tied back to a reviewed commit.
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 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 7.47.1 | 16 / 65 | |
| 7.47.0 | 16 / 65 | |
| 7.46.0 | 16 / 65 | |
| 7.45.1 | 16 / 65 | |
| 7.45.0 | 16 / 65 | |
| 7.44.2 | 16 / 65 | |
| 7.44.1 | 16 / 65 | |
| 7.44.0 | 16 / 65 | |
| 7.43.0 | 16 / 65 | |
| 7.42.0 | 16 / 65 | |
| 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 | |
| 7.35.2 | 16 / 65 | |
| 7.35.1 | 16 / 65 | |
| 7.35.0 | 16 / 65 | |
| 7.34.0 | 16 / 65 | |
| 7.33.0 | 16 / 64 | |
| 7.32.0 | 16 / 64 | |
| 7.31.2 | 16 / 64 | |
| 7.31.1 | 16 / 64 | |
| 7.31.0 | 16 / 64 | |
| 7.30.0 | 16 / 64 | |
| 7.29.0 | 16 / 64 | |
| 7.28.0 | 16 / 64 | |
| 7.27.0 | 15 / 64 | |
| 7.26.2 | 15 / 64 | |
| 7.26.1 | 15 / 64 | |
| 7.26.0 | 15 / 64 |
v7.47.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.47.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.46.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.45.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.45.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.44.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.44.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.44.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.35.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.35.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.35.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.34.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.33.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.30.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.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.