expo-dev-menu
Expo/React Native module with the developer 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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): alanhughes is an established Expo org maintainer with strong track record; transition from brentvatne is a known org handoff. | ai | |
| provenance | no-provenance | AI (provenance): Large Expo monorepo package; lack of Sigstore provenance is consistent across all Expo packages and not a meaningful risk signal here. | ai | |
| phantom-deps | phantom-dep:expo-dev-menu-interface | AI (phantom-deps): expo-dev-menu-interface is a sibling monorepo package used via native config, not direct JS import; stable false positive. | ai |
Versions (showing 51 of 69)
| Version | Deps | Published |
|---|---|---|
| 57.0.9 | 1 / 8 | |
| 57.0.8 | 1 / 8 | |
| 57.0.7 | 1 / 8 | |
| 57.0.6 | 1 / 8 | |
| 57.0.5 | 1 / 8 | |
| 57.0.4 | 1 / 8 | |
| 57.0.3 | 1 / 8 | |
| 57.0.2 | 1 / 8 | |
| 57.0.1 | 1 / 8 | |
| 57.0.0 | 1 / 8 | |
| 56.0.21 | 1 / 8 | |
| 56.0.20 | 1 / 8 | |
| 56.0.19 | 1 / 8 | |
| 56.0.18 | 1 / 8 | |
| 56.0.17 | 1 / 8 | |
| 56.0.16 | 1 / 8 | |
| 56.0.15 | 1 / 8 | |
| 56.0.14 | 1 / 8 | |
| 56.0.13 | 1 / 8 | |
| 56.0.12 | 1 / 8 | |
| 56.0.11 | 1 / 8 | |
| 56.0.10 | 1 / 8 | |
| 56.0.9 | 1 / 8 | |
| 56.0.8 | 1 / 8 | |
| 56.0.7 | 1 / 8 | |
| 56.0.6 | 1 / 8 | |
| 56.0.5 | 1 / 8 | |
| 56.0.4 | 1 / 8 | |
| 56.0.3 | 1 / 8 | |
| 56.0.2 | 1 / 8 | |
| 56.0.1 | 1 / 8 | |
| 56.0.0 | 1 / 7 | |
| 55.0.32 | 1 / 7 | |
| 55.0.31 | 1 / 7 | |
| 55.0.30 | 1 / 7 | |
| 55.0.29 | 1 / 7 | |
| 55.0.28 | 1 / 7 | |
| 55.0.27 | 1 / 7 | |
| 55.0.26 | 1 / 7 | |
| 55.0.25 | 1 / 7 | |
| 55.0.24 | 1 / 7 | |
| 55.0.23 | 1 / 7 | |
| 55.0.22 | 1 / 7 | |
| 55.0.21 | 1 / 7 | |
| 55.0.20 | 1 / 7 | |
| 55.0.19 | 1 / 7 | |
| 55.0.18 | 1 / 7 | |
| 55.0.17 | 1 / 7 | |
| 55.0.16 | 1 / 7 | |
| 55.0.15 | 1 / 7 | |
| 55.0.14 | 1 / 7 |
v57.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (alanhughes) than the most recent previously approved version (brentvatne) on 2026-07-01, but alanhughes is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v57.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v57.0.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (brentvatne) than the most recent previously approved version (alanhughes) on 2026-06-27, but brentvatne is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v56.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.