@expo/config
A library for interacting with the app.json
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Canary releases from the Expo monorepo are published via a different CI pipeline that does not attach gitHead; this is a consistent pattern for @expo/* canary versions and not a malicious signal. | ai | |
| publish-pattern | suspicious-version-number | AI (publish-pattern): Expo uses a well-documented canary versioning scheme (X.Y.Z-canary-YYYYMMDD-commithash); this pattern is consistent across all @expo/* canary releases and is not indicative of malicious activity. | ai | |
| dependencies | unvetted-dep:@expo/babel-preset-cli | AI (dependencies): @expo/babel-preset-cli is an official Expo-scoped package from the same organization (expo/expo-cli repo), used legitimately as a Babel preset for CLI tooling. Not a risk for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Expo package with strong publisher track record; lack of provenance is common and not a concern here. | ai | |
| phantom-deps | phantom-dep:@types/invariant | AI (phantom-deps): @types/invariant is a TypeScript type definition with no runtime code; its presence as a dependency rather than devDependency is a packaging quirk, not a security risk. | ai | |
| dependencies | unvetted-dep:@types/invariant | AI (dependencies): @types/invariant is a benign TypeScript type-only package; no executable code, no security risk regardless of version constraint. | ai | |
| provenance | publisher-changed | AI (provenance): brentvatne is a long-standing Expo core team member; publisher rotation within the Expo org is expected and not a security concern for this package. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @expo/require-utils is a first-party Expo monorepo package; adding it is a routine internal refactor, not a supply-chain risk. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Maintainer changes within the Expo organization are routine; already marked as accepted risk in findings. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): tsapeta and philpl are known Expo org contributors; maintainer rotation within the Expo team is expected and not a takeover signal for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Inflated semver (55.x) reflects Expo's SDK versioning scheme, not spam inflation. Short README is typical for monorepo packages. Not a bogus package. | ai |
Versions (showing 100 of 255)
| Version | Deps | Published |
|---|---|---|
| 6.0.24 | 11 / 1 | |
| 6.0.23 | 11 / 1 | |
| 6.0.22 | 11 / 1 | |
| 6.0.21 | 11 / 1 | |
| 6.0.20 | 11 / 1 | |
| 6.0.19 | 11 / 1 | |
| 6.0.18 | 11 / 1 | |
| 6.0.17 | 11 / 1 | |
| 6.0.16 | 11 / 1 | |
| 6.0.15 | 11 / 1 | |
| 6.0.14 | 11 / 1 | |
| 6.0.13 | 11 / 1 | |
| 6.0.12 | 11 / 1 | |
| 6.0.11 | 11 / 1 | |
| 6.0.10 | 11 / 1 | |
| 6.0.9 | 11 / 1 | |
| 6.0.8 | 11 / 1 | |
| 6.0.7 | 11 / 1 | |
| 6.0.6 | 11 / 1 | |
| 6.0.4 | 11 / 1 | |
| 6.0.3 | 11 / 1 | |
| 6.0.2 | 11 / 1 | |
| 6.0.0 | 11 / 1 | |
| 5.0.9 | 11 / 1 | |
| 5.0.8 | 11 / 1 | |
| 5.0.7 | 11 / 1 | |
| 5.0.6 | 11 / 1 | |
| 5.0.5 | 14 / 3 | |
| 5.0.4 | 14 / 3 | |
| 5.0.3 | 14 / 3 | |
| 5.0.2 | 14 / 3 | |
| 5.0.1 | 14 / 3 | |
| 5.0.0 | 14 / 3 | |
| 4.0.4 | 14 / 3 | |
| 4.0.3 | 14 / 3 | |
| 4.0.2 | 14 / 3 | |
| 4.0.1 | 14 / 3 | |
| 4.0.0 | 14 / 3 | |
| 3.3.43 | 14 / 3 | |
| 3.3.42 | 14 / 3 | |
| 3.3.41 | 14 / 3 | |
| 3.3.40 | 14 / 3 | |
| 3.3.39 | 14 / 3 | |
| 3.3.38 | 14 / 3 | |
| 3.3.37 | 14 / 3 | |
| 3.3.36 | 14 / 3 | |
| 3.3.35 | 14 / 3 | |
| 3.3.34 | 14 / 3 | |
| 3.3.33 | 14 / 3 | |
| 3.3.32 | 14 / 3 | |
| 3.3.31 | 14 / 3 | |
| 3.3.30 | 14 / 3 | |
| 3.3.29 | 12 / 3 | |
| 3.3.28 | 12 / 3 | |
| 3.3.27 | 12 / 3 | |
| 3.3.26 | 12 / 3 | |
| 3.3.25 | 12 / 3 | |
| 3.3.24 | 12 / 3 | |
| 3.3.23 | 12 / 3 | |
| 3.3.22 | 12 / 4 | |
| 3.3.21 | 12 / 4 | |
| 3.3.20 | 12 / 4 | |
| 3.3.19 | 11 / 3 | |
| 3.3.18 | 11 / 3 | |
| 3.3.17 | 11 / 3 | |
| 3.3.16 | 10 / 3 | |
| 3.3.15 | 17 / 5 | |
| 3.3.14 | 17 / 5 | |
| 3.3.13 | 17 / 5 | |
| 3.3.12 | 16 / 5 | |
| 3.3.11 | 16 / 5 | |
| 3.3.10 | 16 / 5 | |
| 3.3.9 | 16 / 5 | |
| 3.3.8 | 16 / 5 | |
| 3.3.7 | 16 / 5 | |
| 3.3.6 | 16 / 5 | |
| 3.3.5 | 16 / 5 | |
| 3.3.4 | 16 / 5 | |
| 3.3.3 | 16 / 5 | |
| 3.3.2 | 16 / 5 | |
| 3.3.1 | 15 / 5 | |
| 3.3.0 | 13 / 5 | |
| 3.2.22 | 13 / 5 | |
| 3.2.21 | 13 / 5 | |
| 3.2.20 | 13 / 5 | |
| 3.2.19 | 12 / 5 | |
| 3.2.18 | 12 / 5 | |
| 3.2.17 | 12 / 5 | |
| 3.2.16 | 12 / 5 | |
| 3.2.15 | 12 / 5 | |
| 3.2.14 | 12 / 5 | |
| 3.2.13 | 12 / 5 | |
| 3.2.12 | 12 / 5 | |
| 3.2.11 | 12 / 5 | |
| 3.2.10 | 12 / 5 | |
| 3.2.9 | 13 / 5 | |
| 3.2.8 | 13 / 4 | |
| 3.2.7 | 13 / 5 | |
| 3.2.6 | 13 / 5 | |
| 3.2.5 | 12 / 6 |
v6.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.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.
v6.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.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.
v6.0.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.
v6.0.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.
v6.0.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.
v6.0.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.
v6.0.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.
v6.0.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.
v6.0.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.
v6.0.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.
v6.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.
v6.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.0.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.
v5.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.
v5.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.
v5.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.
v4.0.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.
v4.0.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.
v4.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.
v4.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.
v4.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.
v3.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.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.
v3.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.3.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.
v3.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.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.
v3.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.
v3.2.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.