Create a new Jest project
84%
Total Score
100
89
83
The repository name does not match create-jest and its README does not mention the package, so the package-to-repository relationship is indirect; this is consistent with a monorepo subpackage but remains a transparency caution.
The project uses established build tooling, though no security-scanning tools were detected; the repository's security policy provides some compensating transparency.
All 11 workflows were analyzed, all 48 action references are pinned, and no untrusted checkout or script-injection sinks were found. The audit also reports high-confidence informational use of trusted publishing and three workflows with top-level write permissions, warranting a limited hygiene caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
chalk Version ^4.1.2 | — | — |
exit-x Version ^0.2.2 | — | — |
prompts Version ^2.4.2 | — | — |
jest-util Version 30.5.1 | — | — |
@jest/types Version 30.5.1 | — | — |
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.