reka-ui
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to CI/CD-attested GitHub Actions publish with SLSA provenance; benign for this established package. | ai | |
| phantom-deps | phantom-dep:@floating-ui/dom | AI (phantom-deps): @floating-ui/dom is a declared runtime dep used transitively; stable false positive for this package. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 2.10.1 | 10 / 27 | |
| 2.10.0 | 10 / 27 | |
| 2.9.10 | 10 / 27 | |
| 2.9.9 | 10 / 26 | |
| 2.9.8 | 10 / 26 | |
| 2.9.7 | 10 / 26 | |
| 2.9.6 | 10 / 26 | |
| 2.9.5 | 10 / 26 | |
| 2.9.4 | 10 / 26 | |
| 2.9.3 | 10 / 23 | |
| 2.9.2 | 10 / 23 | |
| 2.9.1 | 10 / 23 | |
| 2.9.0 | 10 / 23 | |
| 2.8.2 | 10 / 23 | |
| 2.8.0 | 10 / 23 | |
| 2.7.0 | 10 / 23 | |
| 2.6.2 | 10 / 23 | |
| 2.6.1 | 10 / 23 |
v2.9.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.1
2 findingsThis version was published by a different npm account than previous versions on 2026-03-11. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.9.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.