`@expo/eas-build-job` contains types and Joi schemas for job objects. It's used in `eas-cli` to create the job object and on EAS Build workers (and in `eas-cli-local-build-plugin`) to process the job and run the build.
88%
Total Score
healthy
Frequent releases and active organization-backed development outweigh workflow audit and publisher-account hygiene concerns.
The registry has 13 publishers, but several publish through consumer Gmail accounts, including brentvatne, exponent, kudochien, alanhughes, ccheever, szdziedzic, and wschurman; this is an account-hygiene caution despite the active organization-backed project.
The repository name does not match the package name and the signal reports no package-name mention in the README, which creates some ownership ambiguity; the package is nevertheless documented as a subpackage in the provided repository README context.
All 20 workflows were analyzed with no unpinned actions, but the audit reports a high-confidence template-injection finding, archived action use, inherited secrets, and ad hoc package installs. The template-injection finding is not corroborated by an untrusted checkout or script-injection path, so these are workflow hygiene concerns rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
joi Version ^17.13.1 | — | — |
zod Version ^4.3.5 | — | — |
semver Version ^7.6.2 | — | — |
@expo/logger Version 25.0.0 | — | — |
@expo/results Version 1.0.0 | — | — |
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.