@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 51 of 255)
| Version | Deps | Published |
|---|---|---|
| 56.0.9 | 10 / 5 | |
| 56.0.8 | 10 / 5 | |
| 56.0.7 | 10 / 5 | |
| 56.0.6 | 10 / 5 | |
| 56.0.5 | 10 / 5 | |
| 56.0.4 | 10 / 5 | |
| 56.0.3 | 10 / 5 | |
| 56.0.2 | 10 / 5 | |
| 56.0.1 | 10 / 5 | |
| 56.0.0 | 10 / 5 | |
| 55.0.17 | 10 / 2 | |
| 55.0.16 | 10 / 2 | |
| 55.0.15 | 10 / 2 | |
| 55.0.14 | 10 / 2 | |
| 55.0.13 | 11 / 2 | |
| 55.0.12 | 11 / 2 | |
| 55.0.11 | 11 / 2 | |
| 55.0.10 | 11 / 2 | |
| 55.0.9 | 11 / 2 | |
| 55.0.8 | 11 / 2 | |
| 55.0.7 | 11 / 2 | |
| 55.0.6 | 11 / 2 | |
| 55.0.5 | 11 / 2 | |
| 55.0.4 | 13 / 3 | |
| 55.0.3 | 13 / 2 | |
| 55.0.2 | 13 / 2 | |
| 55.0.1 | 13 / 2 | |
| 55.0.0 | 13 / 2 | |
| 12.0.13 | 13 / 2 | |
| 12.0.12 | 13 / 2 | |
| 12.0.11 | 13 / 2 | |
| 12.0.10 | 13 / 2 | |
| 12.0.9 | 13 / 2 | |
| 12.0.8 | 13 / 2 | |
| 12.0.7 | 13 / 2 | |
| 12.0.6 | 13 / 2 | |
| 12.0.5 | 13 / 2 | |
| 12.0.4 | 13 / 2 | |
| 12.0.3 | 13 / 2 | |
| 12.0.2 | 13 / 2 | |
| 12.0.1 | 13 / 2 | |
| 12.0.0 | 13 / 2 | |
| 11.0.13 | 13 / 2 | |
| 11.0.12 | 13 / 2 | |
| 11.0.11 | 13 / 2 | |
| 11.0.10 | 13 / 2 | |
| 11.0.9 | 13 / 2 | |
| 11.0.8 | 13 / 2 | |
| 11.0.7 | 13 / 2 | |
| 11.0.6 | 13 / 2 | |
| 11.0.5 | 13 / 2 |
v56.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.6
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 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.5
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 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v55.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v55.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.8
2 findingsThis version was published by a different npm account than previous versions on 2026-02-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.4
2 findingsThis version was published by a different npm account than previous versions on 2026-02-03. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.3
2 findingsThis version was published by a different npm account than previous versions on 2026-01-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.0.10
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 2025-10-01. This could indicate a legitimate maintainer transition or an account compromise.
v12.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.8
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 2025-09-10. This could indicate a legitimate maintainer transition or an account compromise.
v12.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.6
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 2025-08-31. This could indicate a legitimate maintainer transition or an account compromise.
v12.0.5
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 2025-08-27. This could indicate a legitimate maintainer transition or an account compromise.
v12.0.4
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 2025-08-25. This could indicate a legitimate maintainer transition or an account compromise.
v12.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.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 2025-08-17. This could indicate a legitimate maintainer transition or an account compromise.
v12.0.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 2025-08-15. This could indicate a legitimate maintainer transition or an account compromise.
v12.0.0
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 2025-08-13. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.13
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 2025-07-08. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.12
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 2025-07-03. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.11
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 2025-07-01. This could indicate a legitimate maintainer transition or an account compromise.
v11.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.