Get the prebuild config
88%
Total Score
healthy
Active Expo monorepo with frequent releases and broad contributor activity, though repository references and workflow coverage are incomplete.
The Expo organization provides backing, but several publishing accounts use personal or outside domains, including brentvatne, exponent, kudochien, alanhughes, ccheever, szdziedzic, wschurman, ide, bycedric, tsapeta, philpl, and their listed domains; this is an account-hygiene caution rather than evidence of a thin maintenance team.
The repository name does not match @expo/prebuild-config and its README does not mention the package, creating a provenance-transparency caution; the package file tree nevertheless shows a substantial built package consistent with a monorepo subpackage.
All 136 analyzed action references are pinned, and no untrusted checkout or script-injection sink was found. However, only 30 of 54 workflows were analyzed, with high-confidence template-injection findings and several ad hoc package installs; the listed pull_request_target workflows do not establish a trigger-and-sink combination from the supplied paths.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
debug Version ^4.3.1 | — | — |
semver Version ^7.6.0 | — | — |
@expo/config Version ~57.0.10 | — | — |
resolve-from Version ^5.0.0 | — | — |
@expo/json-file Version ^11.0.1 | — | — |
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.