Functions for converting Expo SDK versions to EAS runtime versions
55%
Total Score
caution
Usable with caveats: only two releases across five years, with a long gap between them.
No build attestation, trusted publisher identity, or staged publishing is present, leaving the artifact's build origin less verifiable. This is a transparency weakness rather than evidence of malicious behavior.
The publisher list includes consumer-domain accounts such as brentvatne, exponent, kudochien, alanhughes, ccheever, szdziedzic, and wschurman using gmail.com, plus outside-domain accounts ide, bycedric, tsapeta, and philpl. This is an account-hygiene concern, although it does not establish a small maintenance team.
The package has only two releases over about five and a half years, with one release in the last 12 months and a roughly five-and-a-half-year median interval. This suggests sparse maintenance activity, though the recent release shows the package is not wholly abandoned.
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.