@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 | missing-githead | AI (provenance): Trusted Radix publisher; publish-env metadata change, no behavioral risk. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore attestation is not a risk for this established package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos is the WorkOS org that acquired Radix UI; legitimate transfer. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped @radix-ui package; missing description is a minor metadata gap, not a risk signal. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Previous individual maintainers replaced by org account after WorkOS acquisition. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance. | 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 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 1.1.24 | 10 / 8 | |
| 1.1.23 | 10 / 8 | |
| 1.1.22 | 10 / 8 | |
| 1.1.21 | 10 / 8 | |
| 1.1.20 | 10 / 8 | |
| 1.1.19 | 10 / 8 | |
| 1.1.18 | 10 / 8 | |
| 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 | |
| 1.1.12 | 10 / 10 | |
| 1.1.11 | 10 / 10 | |
| 1.1.10 | 10 / 10 | |
| 1.1.9 | 10 / 10 | |
| 1.1.8 | 10 / 10 | |
| 1.1.7 | 10 / 9 | |
| 1.1.6 | 10 / 9 | |
| 1.1.5 | 10 / 7 | |
| 1.1.4 | 10 / 0 | |
| 1.1.3 | 10 / 0 | |
| 1.1.2 | 10 / 0 | |
| 1.1.1 | 10 / 0 | |
| 1.1.0 | 10 / 0 | |
| 1.0.4 | 11 / 0 | |
| 1.0.3 | 11 / 0 | |
| 1.0.2 | 11 / 0 | |
| 1.0.1 | 11 / 0 | |
| 1.0.0 | 11 / 0 |
v1.1.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.1.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: chancestrickland.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2024-10-01. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.