84%
Total Score
88
100
95
83
Although 3 contributors were active in the last 3 months, one contributor made about 96% of commits, leaving maintenance capacity highly concentrated. Organization backing provides some handoff capacity but does not remove the concentration concern.
The repository name does not match the package name and its README does not mention this package, creating some ownership ambiguity. The Jest organization backing and the repository's large monorepo structure partly compensate for that gap.
All 11 workflows were analyzed, all 48 action references are pinned, and no untrusted checkout or script-injection sinks were found. The audit reports high-confidence informational use of trusted publishing, which is a mild supply-chain hygiene concern, while top-level write permissions occur in only 3 workflows.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jest-mock Version 30.5.2 | — | — |
jest-util Version 30.5.1 | — | — |
@jest/types Version 30.5.1 | — | — |
@types/node Version * | — | — |
jest-validate 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.