jest-expo-enzyme
A Jest preset that enables you to test your universal Expo & React elements with the Enzyme testing library.
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Expo monorepo packages are commonly published at 0.0.0 as placeholders; this is an official Expo package from a highly trusted publisher with 6083 approved packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Cosmetic README/keyword issues only; package is a legitimate Expo testing utility from the official expo/expo GitHub repo. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @wojtekmaj/enzyme-adapter-react-17 is the standard Enzyme adapter for React 17 and a natural dependency for this testing utility package. | ai | |
| provenance | publisher-changed | AI (provenance): Both tsapeta and brentvatne are well-known Expo team members; this is a legitimate intra-org maintainer transition, not a suspicious takeover. | ai | |
| phantom-deps | phantom-dep:react-test-renderer | AI (phantom-deps): react-test-renderer is a declared runtime dependency used in Jest/Enzyme config files; expected for a testing preset package. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.5.0 | 8 / 3 | |
| 1.4.2 | 8 / 3 | |
| 1.4.1 | 8 / 3 | |
| 1.4.0 | 8 / 3 | |
| 1.3.0 | 8 / 3 | |
| 1.2.5 | 8 / 3 | |
| 1.2.4 | 8 / 3 | |
| 1.2.3 | 8 / 3 | |
| 1.2.2 | 8 / 3 | |
| 1.2.1 | 8 / 3 | |
| 1.2.0 | 8 / 3 | |
| 1.1.2 | 8 / 3 | |
| 1.1.1 | 8 / 3 | |
| 1.1.0 | 8 / 3 | |
| 1.0.4 | 8 / 3 | |
| 1.0.3 | 8 / 3 | |
| 1.0.2 | 8 / 5 | |
| 1.0.1 | 8 / 5 | |
| 1.0.0 | 8 / 5 | |
| 0.0.1 | 8 / 5 | |
| 0.0.0 | 8 / 2 |
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
2 findingsThis version was published by a different npm account than previous versions on 2022-10-28. 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.
v1.4.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 2022-10-25. This could indicate a legitimate maintainer transition or an account compromise.
v1.4.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 2022-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.3.0
2 findingsThis version was published by a different npm account than previous versions on 2022-04-18. 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.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.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 2021-09-28. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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 2020-11-17. This could indicate a legitimate maintainer transition or an account compromise.
v1.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 2020-08-18. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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 2020-05-27. This could indicate a legitimate maintainer transition or an account compromise.
v1.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 2020-02-24. This could indicate a legitimate maintainer transition or an account compromise.
v0.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 2019-11-12. This could indicate a legitimate maintainer transition or an account compromise.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.