The Expo inline modules
84%
Total Score
healthy
Active Expo project with frequent releases; the workflow audit is incomplete and finds template-injection patterns.
The package has 13 registry publishers and is backed by the Expo organization. Several publishers use outside or personal domains, including ide (jameside.com), bycedric (bycedric.com), tsapeta (tsapeta.com), philpl (kitten.sh), and seven gmail.com accounts; this is account-hygiene caution, not evidence of limited maintenance capacity.
The repository name does not match the package and its README does not mention @expo/inline-modules. A monorepo name mismatch is normal, but the missing package mention leaves some uncertainty that this repository is the package's intended source.
The release is not a prerelease, although the package remains below a stable major version and 30% of recent releases are prereleases. This is a modest maturity consideration, not a major dependency risk.
The audit covered only 30 of 54 workflows, so repository workflow coverage is incomplete. It found high-confidence template-injection patterns and high-confidence ad hoc package installs; the pull_request_target workflows had no reported untrusted checkouts or script injection, so these findings warrant caution rather than a severe conclusion.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
@expo/config-plugins Version ~58.0.9 | — | — |
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.