**Note:** More details on user side API can be found in [Jest documentation](https://jestjs.io/docs/mock-function-api).
70%
Total Score
88
89
83
Three contributors were active in the last three months, but one contributor made about 96% of commits. The organization backing reduces the risk somewhat, but this remains a meaningful concentration concern.
The repository name does not match jest-mock and its README does not mention the package. This can be normal for a monorepo, but the absence of both signals creates some uncertainty that the linked repository directly represents this package.
The project uses established build tooling, but no security-scanning tools were detected, leaving a modest transparency and hygiene gap.
All 11 workflows were analyzed with no unpinned action references, untrusted checkouts, or script injections. The audit also found a high-confidence trusted-publishing finding and three workflows with top-level write permissions, which warrant caution despite the otherwise strong results.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jest-util Version 30.5.1 | — | — |
@jest/types Version 30.5.1 | — | — |
@types/node Version * | — | — |
@jest/expect-utils Version 30.5.2 | — | — |
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.