Jest preset for React Native apps
70%
Total Score
caution
Active project backing is offset by risky, mostly unpinned CI workflows and an unusually prerelease-heavy history.
The linked repository does not match the package name and does not mention it in its README. A monorepo explains the name mismatch, but the lack of any package mention leaves a provenance and ownership ambiguity.
The project uses build tooling, but no security scanning tools were detected. The large active project and separate workflow audit provide some compensating evidence, though security-tool coverage is incomplete.
No repository security policy was detected. This is a transparency gap for a large project, although it does not by itself indicate abandonment or unsafe code.
Version 0.88.0 is not a prerelease, but 95% of recent releases were prereleases, which makes the surrounding release stream less stable.
The audit found 88 unpinned actions out of 95, high-confidence template-injection findings, broad inherited secrets, and some write-scoped workflows; 6 of 36 workflows were not analyzed. Pull-request triggers had no reported untrusted checkouts or script injection, but the remaining CI hygiene materially lowers confidence in build controls.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
babel-jest Version ^29.7.0 | — | — |
regenerator-runtime Version ^0.13.2 | — | — |
jest-environment-node Version ^29.7.0 | — | — |
@react-native/js-polyfills Version 0.88.0 | — | — |
@jest/create-cache-key-function Version ^29.7.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.