← Home

@radix-ui/react-popover

View docs [here](https://radix-ui.com/primitives/docs/components/popover).

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

hadihallakchancestricklandmark-workosnpm-workos

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Radix UI moved to GitHub Actions CI/CD publishing with SLSA provenance; organizational transition. ai
maintainer-change maintainer-added AI (maintainer-change): npm-workos is the WorkOS org account now maintaining radix-ui packages. ai
maintainer-change maintainer-removed AI (maintainer-change): Individual maintainers replaced by org-level npm-workos account; expected transition. ai
npm-metadata no-description AI (npm-metadata): Radix UI component packages historically have minimal descriptions. ai
dependencies unvetted-dep:@radix-ui/react-popper AI (dependencies): First-party Radix UI sibling package; stable false positive for this package family. ai
bogus-package bogus-package AI (bogus-package): Radix UI sub-packages consistently lack npm keywords and detailed READMEs; documentation lives on radix-ui.com. This is a stable pattern across the entire monorepo, not a spam signal. ai

Versions (showing 5 of 5)

Version Deps Published
1.1.16 15 / 7
1.1.15 15 / 9
1.1.14 15 / 9
1.1.13 15 / 9
1.1.12 15 / 9

v1.1.16

2 findings
HIGH Publisher changed: chancestrickland → GitHub Actions (on 2026-06-06) provenance

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.

INFO Has SLSA provenance attestation provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.14

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.1.12

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.