Module for executing heavy tasks under forked processes in parallel, by providing a `Promise` based interface, minimum overhead, and bound workers.
82%
Total Score
88
100
89
80
50
No build attestation, trusted publisher, or staged publishing evidence is present, leaving the connection between source and published artifact less transparent. The repository and package structure provide some context but do not replace provenance.
One workflow uses pull_request_target, which warrants review because it runs with elevated trust context, but no untrusted checkout or script-injection patterns were detected across the analyzed workflows.
Three contributors were active recently, but one contributor made about 96% of the commits. The organization-owned repository provides some handoff capacity, yet the current work remains highly concentrated.
The repository name does not match jest-worker and its README does not mention the package, which creates some uncertainty about package ownership. The Jest organization and the package's clear Jest-specific README context provide partial compensation, but the linkage is still less explicit.
The repository uses established build tools and has a build system, but no security scanning tools were detected. This is a transparency and process gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
jest-util Version 30.5.1 | — | — |
@types/node Version * | — | — |
merge-stream Version ^2.0.0 | — | — |
supports-color Version ^8.1.1 | — | — |
@ungap/structured-clone Version ^1.3.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.