@radix-ui/react-hover-card
View docs [here](https://radix-ui.com/primitives/docs/components/hover-card).
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous individual maintainers replaced by org account; legitimate transition. | ai | |
| provenance | missing-githead | AI (provenance): Consistent with GitHub Actions publish flow; SLSA provenance present instead. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos is the WorkOS org account; WorkOS acquired Radix UI. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing for the radix-ui org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Radix UI component packages consistently omit descriptions; not indicative of malicious intent. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI component packages intentionally have minimal READMEs and no keywords; not spam. | ai | |
| provenance | no-provenance | AI (provenance): Established Radix UI package; lack of Sigstore provenance is not a risk signal here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.16 | 9 / 7 | |
| 1.1.15 | 9 / 9 | |
| 1.1.6 | 9 / 8 | |
| 1.1.3 | 9 / 0 | |
| 1.1.1 | 9 / 0 |
v1.1.16
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-06-06. 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.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
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.1.3
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.1.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.