@radix-ui/react-menubar
View docs [here](https://radix-ui.com/primitives/docs/components/menubar).
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos is the WorkOS org that acquired Radix UI; legitimate transfer. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous individual maintainers replaced by org account after WorkOS acquisition. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped @radix-ui package; missing description is a minor metadata gap, not a risk signal. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-menu | AI (dependencies): Sibling Radix UI package from the same org; expected dependency for this menubar primitive. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Radix UI sub-packages consistently have minimal READMEs and no keywords; documentation lives at radix-ui.com. This is a stable pattern across the monorepo, not a spam indicator. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.1.17 | 10 / 8 | |
| 1.1.16 | 10 / 10 | |
| 1.1.15 | 10 / 10 | |
| 1.1.14 | 10 / 10 | |
| 1.1.13 | 10 / 10 |
v1.1.17
2 findingsThis 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.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.