@radix-ui/react-navigation-menu
View docs [here](https://radix-ui.com/primitives/docs/components/navigation-menu).
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): Build-env metadata change on official radix-ui monorepo; no behavioral risk. | ai | |
| provenance | publisher-changed | AI (provenance): Legitimate transition to GitHub Actions CI/CD publishing with SLSA provenance. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): npm-workos reflects WorkOS acquisition of Radix UI; legitimate org change. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old individual maintainers replaced by org account; expected during corporate transition. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Radix monorepo packages often omit description; not a risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): False positive on a 36M downloads/week established package. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.2.22 | 14 / 8 | |
| 1.2.21 | 14 / 8 | |
| 1.2.20 | 14 / 8 | |
| 1.2.19 | 14 / 8 | |
| 1.2.18 | 14 / 8 | |
| 1.2.17 | 14 / 8 | |
| 1.2.16 | 14 / 7 | |
| 1.2.15 | 14 / 7 | |
| 1.2.14 | 14 / 9 | |
| 1.2.13 | 14 / 9 | |
| 1.2.12 | 14 / 9 | |
| 1.2.11 | 14 / 9 | |
| 1.2.10 | 14 / 9 | |
| 1.2.9 | 14 / 9 | |
| 1.2.8 | 14 / 9 | |
| 1.2.7 | 14 / 9 | |
| 1.2.6 | 14 / 8 | |
| 1.2.5 | 14 / 8 | |
| 1.2.4 | 14 / 6 | |
| 1.2.3 | 14 / 0 | |
| 1.2.2 | 14 / 0 | |
| 1.2.1 | 14 / 0 | |
| 1.2.0 | 14 / 0 | |
| 1.1.4 | 15 / 0 | |
| 1.1.3 | 15 / 0 | |
| 1.1.2 | 15 / 0 | |
| 1.1.1 | 15 / 0 | |
| 1.1.0 | 15 / 0 | |
| 1.0.0 | 15 / 0 |
v1.2.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.2.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.2.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.2.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.2.7
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.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.