jest-expo
A Jest preset to painlessly test your Expo / React Native apps.
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 | publisher-changed | AI (provenance): brentvatne is a core Expo team member with an extensive trusted publishing history; expo-bot → brentvatne transitions are normal for this monorepo package. | ai | |
| phantom-deps | phantom-dep:json5 | AI (phantom-deps): json5 is a declared dependency referenced in config files; phantom-dep finding is a false positive for this Jest preset package. | ai | |
| phantom-deps | phantom-dep:babel-jest | AI (phantom-deps): babel-jest is a declared dependency referenced in Jest config files; expected pattern for a Jest preset. | ai | |
| phantom-deps | phantom-dep:react-test-renderer | AI (phantom-deps): react-test-renderer is a declared dependency referenced in Jest config/preset files; expected pattern for a Jest preset. | ai | |
| phantom-deps | phantom-dep:jest-environment-jsdom | AI (phantom-deps): jest-environment-jsdom is a declared dependency referenced in Jest config files; expected pattern for a Jest preset. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process usage is in bin/jest.js, a standard Jest CLI wrapper binary — expected and benign for this package. | ai |
Versions (showing 100 of 186)
| Version | Deps | Published |
|---|---|---|
| 56.0.4 | 12 / 3 | |
| 56.0.3 | 12 / 3 | |
| 56.0.2 | 12 / 3 | |
| 56.0.1 | 12 / 3 | |
| 56.0.0 | 12 / 2 | |
| 55.0.18 | 14 / 1 | |
| 55.0.17 | 14 / 1 | |
| 55.0.16 | 14 / 1 | |
| 55.0.15 | 14 / 1 | |
| 55.0.14 | 14 / 1 | |
| 55.0.13 | 14 / 1 | |
| 55.0.12 | 14 / 1 | |
| 55.0.11 | 14 / 1 | |
| 55.0.10 | 14 / 1 | |
| 55.0.9 | 14 / 1 | |
| 55.0.8 | 14 / 1 | |
| 55.0.7 | 14 / 1 | |
| 55.0.6 | 14 / 1 | |
| 55.0.5 | 14 / 1 | |
| 55.0.4 | 14 / 1 | |
| 55.0.3 | 14 / 1 | |
| 55.0.2 | 14 / 1 | |
| 55.0.1 | 14 / 1 | |
| 55.0.0 | 14 / 1 | |
| 54.0.17 | 14 / 1 | |
| 54.0.16 | 14 / 1 | |
| 54.0.15 | 14 / 1 | |
| 54.0.14 | 14 / 1 | |
| 54.0.13 | 15 / 0 | |
| 54.0.12 | 15 / 0 | |
| 54.0.11 | 15 / 0 | |
| 54.0.10 | 15 / 0 | |
| 54.0.9 | 15 / 0 | |
| 54.0.8 | 16 / 0 | |
| 54.0.7 | 16 / 0 | |
| 54.0.6 | 16 / 0 | |
| 54.0.5 | 16 / 0 | |
| 54.0.4 | 16 / 0 | |
| 54.0.3 | 16 / 0 | |
| 54.0.2 | 16 / 0 | |
| 54.0.1 | 16 / 0 | |
| 54.0.0 | 16 / 0 | |
| 53.0.14 | 15 / 1 | |
| 53.0.13 | 15 / 1 | |
| 53.0.12 | 15 / 1 | |
| 53.0.11 | 15 / 1 | |
| 53.0.10 | 16 / 0 | |
| 53.0.9 | 16 / 0 | |
| 53.0.8 | 16 / 0 | |
| 53.0.7 | 16 / 0 | |
| 53.0.6 | 16 / 0 | |
| 53.0.5 | 16 / 0 | |
| 53.0.4 | 16 / 0 | |
| 53.0.3 | 16 / 0 | |
| 53.0.2 | 16 / 0 | |
| 53.0.1 | 16 / 0 | |
| 53.0.0 | 16 / 0 | |
| 52.0.6 | 17 / 0 | |
| 52.0.5 | 17 / 0 | |
| 52.0.4 | 17 / 0 | |
| 52.0.3 | 17 / 0 | |
| 52.0.2 | 17 / 0 | |
| 52.0.1 | 17 / 0 | |
| 52.0.0 | 17 / 0 | |
| 51.0.4 | 12 / 0 | |
| 51.0.3 | 12 / 0 | |
| 51.0.2 | 12 / 0 | |
| 51.0.1 | 12 / 0 | |
| 51.0.0 | 12 / 0 | |
| 50.0.4 | 12 / 0 | |
| 50.0.3 | 12 / 0 | |
| 50.0.2 | 12 / 0 | |
| 50.0.1 | 12 / 0 | |
| 50.0.0 | 12 / 0 | |
| 49.0.0 | 10 / 0 | |
| 48.0.2 | 10 / 0 | |
| 48.0.1 | 10 / 0 | |
| 48.0.0 | 10 / 0 | |
| 47.0.1 | 9 / 0 | |
| 47.0.0 | 9 / 0 | |
| 46.0.2 | 9 / 0 | |
| 46.0.1 | 9 / 0 | |
| 46.0.0 | 9 / 0 | |
| 45.0.1 | 9 / 0 | |
| 45.0.0 | 9 / 0 | |
| 44.0.1 | 9 / 0 | |
| 44.0.0 | 10 / 0 | |
| 43.0.1 | 10 / 0 | |
| 43.0.0 | 10 / 0 | |
| 42.1.0 | 9 / 0 | |
| 42.0.1 | 9 / 0 | |
| 42.0.0 | 8 / 0 | |
| 41.0.0 | 8 / 0 | |
| 40.0.2 | 8 / 0 | |
| 40.0.1 | 8 / 0 | |
| 40.0.0 | 8 / 0 | |
| 39.0.0 | 8 / 0 | |
| 38.0.2 | 8 / 1 | |
| 38.0.1 | 8 / 1 | |
| 38.0.0 | 8 / 1 |
v56.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.3
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 2026-05-15. This could indicate a legitimate maintainer transition or an account compromise.
v56.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 2026-05-14. This could indicate a legitimate maintainer transition or an account compromise.
v56.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v56.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.18
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 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
v55.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.16
1 findingPackage 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v55.0.10
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. 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.9
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.8
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. 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
2 findingsThis version was published by a different npm account than previous versions on 2026-02-20. 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.6
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.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-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.3
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.2
2 findingsThis version was published by a different npm account than previous versions on 2026-01-22. 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
2 findingsThis version was published by a different npm account than previous versions on 2026-01-22. 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.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.
v54.0.17
2 findingsThis version was published by a different npm account than previous versions on 2026-01-31. 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.
v54.0.16
2 findingsThis version was published by a different npm account than previous versions on 2025-12-12. 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.
v54.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v54.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v53.0.13
2 findingsThis version was published by a different npm account than previous versions on 2025-12-12. 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.
v53.0.12
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. 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.
v53.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v53.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v52.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v51.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.