expo-modules-core
The core of Expo Modules architecture
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 | publisher-changed | AI (provenance): brentvatne is a core Expo team member; transition from expo-bot (CI publisher) to a named maintainer is a routine organizational change within the same org. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval('require') is an intentional bundler-escape pattern to prevent static analysis of node:crypto require; input is not user-controlled. Stable pattern in the Expo codebase. | ai |
Versions (showing 100 of 235)
| Version | Deps | Published |
|---|---|---|
| 2.0.5 | 1 / 2 | |
| 2.0.4 | 1 / 2 | |
| 2.0.3 | 1 / 2 | |
| 2.0.2 | 1 / 2 | |
| 2.0.1 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.12.26 | 1 / 2 | |
| 1.12.25 | 1 / 2 | |
| 1.12.24 | 1 / 2 | |
| 1.12.23 | 1 / 2 | |
| 1.12.22 | 1 / 2 | |
| 1.12.21 | 1 / 2 | |
| 1.12.20 | 1 / 2 | |
| 1.12.19 | 1 / 2 | |
| 1.12.18 | 1 / 2 | |
| 1.12.17 | 1 / 2 | |
| 1.12.16 | 1 / 2 | |
| 1.12.15 | 1 / 2 | |
| 1.12.14 | 1 / 2 | |
| 1.12.13 | 1 / 2 | |
| 1.12.12 | 1 / 2 | |
| 1.12.11 | 1 / 2 | |
| 1.12.10 | 1 / 2 | |
| 1.12.9 | 1 / 2 | |
| 1.12.8 | 1 / 2 | |
| 1.12.7 | 1 / 2 | |
| 1.12.6 | 1 / 2 | |
| 1.12.5 | 1 / 2 | |
| 1.12.4 | 1 / 2 | |
| 1.12.3 | 1 / 2 | |
| 1.12.2 | 1 / 2 | |
| 1.12.1 | 1 / 2 | |
| 1.12.0 | 1 / 2 | |
| 1.11.14 | 1 / 2 | |
| 1.11.13 | 1 / 2 | |
| 1.11.12 | 1 / 2 | |
| 1.11.11 | 1 / 2 | |
| 1.11.10 | 1 / 2 | |
| 1.11.9 | 1 / 2 | |
| 1.11.8 | 1 / 2 | |
| 1.11.7 | 1 / 2 | |
| 1.11.6 | 1 / 2 | |
| 1.11.5 | 1 / 2 | |
| 1.11.4 | 1 / 2 | |
| 1.11.3 | 1 / 2 | |
| 1.11.2 | 1 / 2 | |
| 1.11.1 | 1 / 2 | |
| 1.11.0 | 1 / 2 | |
| 1.10.0 | 1 / 2 | |
| 1.9.0 | 1 / 2 | |
| 1.8.0 | 1 / 2 | |
| 1.7.0 | 2 / 2 | |
| 1.6.0 | 2 / 2 | |
| 1.5.13 | 2 / 2 | |
| 1.5.12 | 2 / 2 | |
| 1.5.11 | 2 / 2 | |
| 1.5.10 | 2 / 2 | |
| 1.5.9 | 2 / 2 | |
| 1.5.8 | 2 / 2 | |
| 1.5.7 | 2 / 2 | |
| 1.5.6 | 2 / 2 | |
| 1.5.5 | 2 / 2 | |
| 1.5.4 | 2 / 2 | |
| 1.5.3 | 2 / 2 | |
| 1.5.2 | 2 / 2 | |
| 1.5.1 | 2 / 2 | |
| 1.5.0 | 2 / 2 | |
| 1.4.0 | 2 / 2 | |
| 1.3.2 | 2 / 2 | |
| 1.3.1 | 2 / 2 | |
| 1.3.0 | 2 / 2 | |
| 1.2.7 | 2 / 2 | |
| 1.2.6 | 2 / 2 | |
| 1.2.5 | 2 / 2 | |
| 1.2.4 | 2 / 2 | |
| 1.2.3 | 2 / 2 | |
| 1.2.2 | 2 / 2 | |
| 1.2.1 | 2 / 2 | |
| 1.2.0 | 2 / 2 | |
| 1.1.1 | 2 / 2 | |
| 1.1.0 | 2 / 2 | |
| 1.0.4 | 2 / 2 | |
| 1.0.3 | 2 / 2 | |
| 1.0.2 | 2 / 2 | |
| 1.0.1 | 2 / 2 | |
| 1.0.0 | 2 / 2 | |
| 0.13.4 | 2 / 2 | |
| 0.13.3 | 2 / 2 | |
| 0.13.2 | 2 / 2 | |
| 0.13.1 | 2 / 2 | |
| 0.13.0 | 2 / 2 | |
| 0.12.0 | 2 / 2 | |
| 0.11.10 | 2 / 2 | |
| 0.11.9 | 2 / 2 | |
| 0.11.8 | 2 / 2 | |
| 0.11.7 | 2 / 2 | |
| 0.11.6 | 2 / 2 | |
| 0.11.5 | 2 / 2 | |
| 0.11.4 | 2 / 2 | |
| 0.11.3 | 2 / 2 |
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.