The Expo SDK
88%
Total Score
healthy
Active, well-supported project with strong release and contributor activity; workflow audit gaps keep it below top health.
No build attestation or trusted-publisher provenance is present, leaving publication origin less independently verifiable despite the package's strong maintenance evidence.
The organization-backed project has 13 registry publishers, but several accounts use consumer or outside domains, including brentvatne, exponent, kudochien, alanhughes, ccheever, szdziedzic, wschurman, ide, bycedric, tsapeta, and philpl. This is account hygiene caution, partly offset by the expo.io organization backing.
The audit covered only 30 of 54 workflows, so it is incomplete. It found high-confidence template-injection patterns in several workflows; template injection alone is a hygiene concern, while the two pull_request_target workflows had no untrusted checkout or script-injection counts.
| Title | Versions | Severity |
|---|---|---|
CVE-2023-28131 expo is vulnerable to Insufficiently Protected Credentials in versions 0.0.0 - 48.0.0. | 0.0.0 - 48.0.0 | Critical |
CVE-2020-24653 expo is vulnerable to Security Vulnerability in versions 0.0.0 - 9.1.0. | 0.0.0 - 9.1.0 | Critical |
| Dependency | Last Release | Score |
|---|---|---|
@expo/cli Version ^57.0.28 | — | — |
expo-font Version ~57.0.4 | — | — |
expo-asset Version ~57.0.19 | — | — |
@expo/metro Version ~56.0.2 | — | — |
@expo/config Version ~57.0.10 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.