70%
Total Score
88
100
94
83
50
No build attestation or staged-publishing provenance is available, leaving publication origin less independently verifiable than it could be.
Three contributors were active, but one contributor made about 96% of the 73 recent commits. Organization backing partly offsets this concentration, but it remains a maintenance-continuity concern.
The repository name differs from the package name and its README does not mention @jest/fake-timers. This is plausible for a monorepo sub-package, but the missing explicit association leaves some ownership ambiguity.
All 11 workflows were analyzed, none of 48 action references were unpinned, and no untrusted checkout or script-injection sink was found. The high-confidence use-trusted-publishing finding indicates long-lived registry credentials instead of short-lived credentials, which is a supply-chain hygiene concern.
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-message-util 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.