Stable client identifier for EAS services
86%
Total Score
healthy
Active Expo-backed maintenance and frequent releases outweigh repository and workflow hygiene gaps.
The repository name does not match the package and its README does not mention expo-eas-client. A monorepo name mismatch is ordinary, but the lack of a package mention leaves some ownership ambiguity.
The audit analyzed only 30 of 54 workflows and found 18 high-confidence template-injection findings, plus high-confidence adhoc package installs; template injection is a workflow hygiene concern here, while no untrusted checkout or script-injection sink was found.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.