@cloud-ru/uikit-product-site-header
SiteHeader
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/alert | AI (dependencies): Legitimate UI library dependency; no malware indicators. | ai | |
| dependencies | unvetted-dep:@snack-uikit/avatar | AI (dependencies): Legitimate UI library dependency; no malware indicators. | ai | |
| dependencies | unvetted-dep:@snack-uikit/button | AI (dependencies): Legitimate UI library dependency; no malware indicators. | ai | |
| dependencies | unvetted-dep:@snack-uikit/divider | AI (dependencies): Legitimate UI library dependency; no malware indicators. | ai | |
| dependencies | unvetted-dep:@snack-uikit/dropdown | AI (dependencies): Legitimate UI library dependency; no malware indicators. | ai | |
| dependencies | unvetted-dep:@snack-uikit/typography | AI (dependencies): Legitimate UI library dependency; no malware indicators. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-icons | AI (dependencies): Same publisher's sibling package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-utils | AI (dependencies): Same publisher's sibling package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-site-layout | AI (dependencies): Same publisher's sibling package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-mobile-modal | AI (dependencies): Same publisher's sibling package; no malware indicators. | ai | |
| dependencies | unvetted-dep:@cloud-ru/uikit-product-button-predefined | AI (dependencies): Same publisher's sibling package; no malware indicators. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is common (~88% of npm); no other risk signals present. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 14 / 0 | |
| 1.6.1 | 14 / 0 | |
| 1.6.0 | 14 / 0 | |
| 1.5.7 | 12 / 0 | |
| 1.5.6 | 12 / 0 | |
| 1.5.5 | 12 / 0 | |
| 1.5.4 | 12 / 0 | |
| 1.5.3 | 12 / 0 | |
| 1.5.2 | 12 / 0 | |
| 1.5.1 | 12 / 0 | |
| 1.5.0 | 12 / 0 | |
| 1.4.3 | 12 / 0 | |
| 1.4.2 | 12 / 0 | |
| 1.4.1 | 12 / 0 | |
| 1.4.0 | 12 / 0 | |
| 1.3.1 | 12 / 0 | |
| 1.3.0 | 12 / 0 | |
| 1.2.2 | 12 / 0 | |
| 1.2.1 | 12 / 0 | |
| 1.2.0 | 12 / 0 | |
| 1.1.2 | 12 / 0 | |
| 1.1.1 | 12 / 0 | |
| 1.1.0 | 12 / 0 | |
| 0.7.1 | 12 / 0 | |
| 0.7.0 | 12 / 0 | |
| 0.6.5 | 12 / 0 | |
| 0.6.4 | 12 / 0 | |
| 0.6.3 | 12 / 0 | |
| 0.6.2 | 12 / 0 | |
| 0.6.1 | 12 / 0 | |
| 0.6.0 | 12 / 0 | |
| 0.5.5 | 11 / 0 | |
| 0.5.4 | 11 / 0 | |
| 0.5.3 | 11 / 0 | |
| 0.5.2 | 11 / 0 | |
| 0.5.1 | 11 / 0 | |
| 0.5.0 | 11 / 0 | |
| 0.4.11 | 11 / 0 | |
| 0.4.10 | 11 / 0 | |
| 0.4.9 | 11 / 0 | |
| 0.4.8 | 11 / 0 |
v1.6.2
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. 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. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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.
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.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
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.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.