jest-worker
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | source-size-tripled | AI (source-diff): jest-worker v25.0.0 is a major version release from the Facebook/Jest monorepo; size increase reflects legitimate feature expansion (thread/process worker support), not injected payload. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): jest-worker 0.0.0 is a name-reservation placeholder by the Jest core team (cpojer); the 0.0.0 version pattern is intentional and not indicative of malice. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Placeholder version from a highly trusted publisher (cpojer/Jest team); sparse metadata is expected for a name-reservation stub, not a spam or malicious package. | ai | |
| dependencies | unvetted-dep:jest-util | AI (dependencies): jest-util is a core Jest monorepo package, a long-standing dependency of jest-worker; not a risk. | ai | |
| dependencies | unvetted-dep:merge-stream | AI (dependencies): merge-stream is a well-known, stable utility package that has been a dependency of jest-worker for many versions. | ai | |
| dependencies | unvetted-dep:@ungap/structured-clone | AI (dependencies): @ungap/structured-clone is a well-known polyfill package, a long-standing dependency of jest-worker; not a risk. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): jest-util is a first-party Jest package pinned to the same version; @ungap/structured-clone is a well-known polyfill. Both are legitimate additions for v30. | ai | |
| provenance | publisher-changed | AI (provenance): cpojer is a founding Jest maintainer; publisher change reflects the Jest project's OpenJS Foundation transition, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (cpojer, rickhanlonii, aaronabramov, openjs-operations) are known Jest core contributors consistent with OpenJS Foundation migration. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removed maintainers are former Facebook/Meta employees; removal is consistent with the documented Jest project transfer to OpenJS Foundation. | ai | |
| npm-metadata | no-description | AI (npm-metadata): jest-worker is a well-known monorepo package; missing description is a cosmetic issue, not a risk indicator. | ai | |
| provenance | no-provenance | AI (provenance): jest-worker is published from the official jestjs/jest monorepo by a long-standing trusted publisher; lack of Sigstore provenance is not a meaningful risk here. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): @types/node is intentionally listed as a runtime dep in Jest packages to expose Node types to consumers; not a security concern. | ai |
Versions (showing 51 of 92)
| Version | Deps | Published |
|---|---|---|
| 30.4.1 | 5 / 7 | |
| 30.4.0 | 5 / 7 | |
| 30.3.0 | 5 / 7 | |
| 30.2.0 | 5 / 7 | |
| 30.1.0 | 5 / 7 | |
| 30.0.5 | 5 / 7 | |
| 30.0.2 | 5 / 7 | |
| 30.0.1 | 5 / 7 | |
| 30.0.0 | 5 / 7 | |
| 29.7.0 | 4 / 8 | |
| 29.6.4 | 4 / 8 | |
| 29.6.3 | 4 / 8 | |
| 29.6.2 | 4 / 8 | |
| 29.6.1 | 4 / 8 | |
| 29.6.0 | 4 / 8 | |
| 29.5.0 | 4 / 8 | |
| 29.4.3 | 4 / 8 | |
| 29.4.2 | 4 / 8 | |
| 29.4.1 | 4 / 7 | |
| 29.4.0 | 4 / 7 | |
| 29.3.1 | 4 / 7 | |
| 29.3.0 | 4 / 7 | |
| 29.2.1 | 4 / 7 | |
| 29.2.0 | 4 / 7 | |
| 29.1.2 | 4 / 7 | |
| 29.1.0 | 3 / 7 | |
| 29.0.3 | 3 / 7 | |
| 29.0.2 | 3 / 7 | |
| 29.0.1 | 3 / 7 | |
| 29.0.0 | 3 / 7 | |
| 28.1.3 | 3 / 7 | |
| 28.1.1 | 3 / 7 | |
| 28.1.0 | 3 / 7 | |
| 28.0.2 | 3 / 7 | |
| 28.0.1 | 3 / 5 | |
| 28.0.0 | 3 / 5 | |
| 27.5.1 | 3 / 5 | |
| 27.5.0 | 3 / 5 | |
| 27.4.6 | 3 / 5 | |
| 27.4.5 | 3 / 5 | |
| 27.4.4 | 3 / 5 | |
| 27.4.2 | 3 / 5 | |
| 27.4.1 | 3 / 5 | |
| 27.4.0 | 3 / 5 | |
| 27.3.1 | 3 / 5 | |
| 27.3.0 | 3 / 5 | |
| 27.2.5 | 3 / 5 | |
| 27.2.4 | 3 / 5 | |
| 27.2.3 | 3 / 5 | |
| 27.2.2 | 3 / 5 | |
| 27.2.0 | 3 / 5 |
v30.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v30.4.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-07. This could indicate a legitimate maintainer transition or an account compromise.
v28.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v28.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v27.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.