@radix-ui/react-context-menu
View docs [here](https://radix-ui.com/primitives/docs/components/context-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@radix-ui/react-menu | AI (dependencies): @radix-ui/react-menu is a core Radix UI primitive and a stable expected dependency of this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI monorepo sub-packages consistently have minimal READMEs and no keywords; this is a structural pattern of the project, not a spam indicator. | ai | |
| provenance | no-provenance | AI (provenance): Radix UI packages are published without Sigstore provenance attestation; this is consistent across all versions and not a security concern given the established publisher. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.2.16 | 6 / 10 | |
| 2.2.15 | 6 / 10 | |
| 2.2.14 | 6 / 10 | |
| 2.2.13 | 6 / 10 |
v2.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.