@reach/menu-button
Accessible React button 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 |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Build tooling changed to tsdx in this version; missing gitHead is a side effect of the new build environment, not an indicator of tampering. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): prop-types is a canonical React ecosystem package; adding it as a runtime dep for a React UI component is entirely expected and benign. | ai | |
| provenance | publisher-changed | AI (provenance): ryanflorence and mjackson are co-founders of the same org (Remix/React Training); this is a documented internal maintainer transition, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mjackson is a well-known, long-standing collaborator in the same org as ryanflorence; addition is a legitimate internal handoff. | ai | |
| provenance | no-provenance | AI (provenance): Reach UI predates provenance attestation; no provenance is expected for this package's era. | ai | |
| bogus-package | bogus-package | AI (bogus-package): chancestrickland is the legitimate maintainer of @reach/* with 1775 approved packages; spam flag is a false positive. | ai | |
| email-domain | unclaimed-email:ryanflorence | AI (email-domain): The 'email' field contains a Twitter handle (@ryanflorence), not a real email address. No actual domain hijacking risk; publisher identity is well-established across 1352 approved packages. | ai | |
| phantom-deps | phantom-dep:warning | AI (phantom-deps): The 'warning' package is a legitimate runtime dep used in React ecosystem packages; phantom-dep flag is a minor packaging artifact, not a security concern. | ai |
Versions (showing 67 of 67)
| Version | Deps | Published |
|---|---|---|
| 0.18.0 | 4 / 7 | |
| 0.17.0 | 6 / 3 | |
| 0.16.2 | 6 / 3 | |
| 0.16.1 | 6 / 3 | |
| 0.16.0 | 6 / 3 | |
| 0.15.3 | 6 / 2 | |
| 0.15.2 | 7 / 2 | |
| 0.15.1 | 7 / 2 | |
| 0.15.0 | 6 / 2 | |
| 0.14.0 | 6 / 2 | |
| 0.13.2 | 6 / 2 | |
| 0.13.1 | 6 / 2 | |
| 0.13.0 | 6 / 0 | |
| 0.12.1 | 6 / 0 | |
| 0.12.0 | 6 / 0 | |
| 0.11.2 | 6 / 0 | |
| 0.11.1 | 6 / 0 | |
| 0.11.0 | 6 / 0 | |
| 0.10.5 | 6 / 0 | |
| 0.10.4 | 6 / 0 | |
| 0.10.3 | 6 / 0 | |
| 0.10.2 | 6 / 0 | |
| 0.10.1 | 6 / 0 | |
| 0.10.0 | 7 / 0 | |
| 0.9.1 | 7 / 0 | |
| 0.9.0 | 7 / 0 | |
| 0.8.6 | 7 / 0 | |
| 0.8.5 | 7 / 0 | |
| 0.8.4 | 7 / 0 | |
| 0.8.3 | 7 / 0 | |
| 0.8.2 | 7 / 0 | |
| 0.8.0 | 5 / 0 | |
| 0.7.4 | 5 / 0 | |
| 0.7.3 | 5 / 0 | |
| 0.7.2 | 5 / 0 | |
| 0.7.1 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.4 | 7 / 0 | |
| 0.6.3 | 7 / 0 | |
| 0.6.2 | 7 / 0 | |
| 0.6.1 | 7 / 4 | |
| 0.5.4 | 7 / 4 | |
| 0.5.3 | 7 / 4 | |
| 0.5.0 | 7 / 4 | |
| 0.4.0 | 7 / 4 | |
| 0.3.0 | 7 / 4 | |
| 0.1.18 | 6 / 4 | |
| 0.1.17 | 6 / 4 | |
| 0.1.16 | 6 / 5 | |
| 0.1.15 | 6 / 5 | |
| 0.1.14 | 6 / 4 | |
| 0.1.13 | 6 / 4 | |
| 0.1.12 | 7 / 3 | |
| 0.1.11 | 7 / 3 | |
| 0.1.10 | 7 / 3 | |
| 0.1.9 | 7 / 3 | |
| 0.1.8 | 7 / 3 | |
| 0.1.7 | 7 / 3 | |
| 0.1.6 | 7 / 3 | |
| 0.1.5 | 7 / 3 | |
| 0.1.4 | 7 / 3 | |
| 0.1.3 | 7 / 3 | |
| 0.1.2 | 7 / 3 | |
| 0.1.1 | 7 / 3 | |
| 0.1.0 | 7 / 3 | |
| 0.0.2 | 5 / 3 | |
| 0.0.1 | 5 / 3 |
v0.18.0
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.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
2 findings[Accepted risk] Package 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 2021-07-10. This could indicate a legitimate maintainer transition or an account compromise.
v0.15.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
2 findings[Accepted risk] Package 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 2020-11-27. This could indicate a legitimate maintainer transition or an account compromise.
v0.12.0
2 findings[Accepted risk] Package 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 2020-11-26. This could indicate a legitimate maintainer transition or an account compromise.
v0.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
3 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.
This version was published by a different npm account than previous versions on 2020-01-09. 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.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2019-10-23. 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.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2019-10-11. 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.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.
v0.1.13
2 findingsMaintainer email '@ryanflorence' uses domain 'ryanflorence' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.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.
v0.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.