@radix-ui/react-dropdown-menu
View docs [here](https://radix-ui.com/primitives/docs/components/dropdown-menu).
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): WorkOS acquisition of Radix UI; new maintainers are known org members. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy due to org transition; resumed publishing under new ownership. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI primitives use minimal READMEs by convention; not spam. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate org transition (WorkOS/Radix); chancestrickland is established publisher. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old Radix maintainers replaced by WorkOS team as part of known transition. | ai | |
| provenance | no-provenance | AI (provenance): Radix UI primitives predate Sigstore provenance adoption; absence is expected for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Radix UI primitives consistently omit descriptions; not indicative of malice for this well-known package family. | ai |
v2.1.16
2 findingsThis version was published by a different npm account than previous versions on 2025-08-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.