← Home

jest-message-util

8
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

aaronabramovsimenbrickhanloniiopenjs-operationscpojer

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): New deps (@jest/types, graceful-fs, @types/stack-utils) are all legitimate, well-known packages consistent with Jest v26 refactoring. ai
provenance publisher-changed AI (provenance): Publisher change from cpojer to simenb reflects a legitimate Jest team transition at Facebook; simenb is a well-known Jest core contributor with a strong track record. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are known Jest/Facebook contributors; this reflects the documented Jest team evolution, not a takeover. ai
maintainer-change maintainer-removed AI (maintainer-change): Removed maintainers are consistent with team changes within the Jest project at Facebook; no compromise indicators. ai
dependencies unvetted-dep:@jest/types AI (dependencies): @jest/types is a core Jest monorepo package; always co-released with jest-message-util at the same version. Stable false positive for this package. ai
dependencies unvetted-dep:stack-utils AI (dependencies): stack-utils is a well-known, stable utility used by Jest for stack trace parsing. No security concerns. ai
dependencies unvetted-dep:@types/stack-utils AI (dependencies): Type definitions package for stack-utils; no runtime risk. Stable false positive for this package. ai
npm-metadata suspicious-initial-version AI (npm-metadata): [email protected] is a well-known Jest monorepo placeholder version published by the core Jest maintainer; 0.0.0 is a standard stub pattern in this ecosystem. ai
npm-metadata no-description AI (npm-metadata): Jest monorepo internal utility; missing description is standard for such packages and not a risk signal. ai
phantom-deps phantom-dep:@types/stack-utils AI (phantom-deps): @types/stack-utils is a TypeScript type declaration used at compile time, not imported at runtime. Phantom-dep detection is a stable false positive for @types/* packages. ai
bogus-package bogus-package AI (bogus-package): Monorepo-published package; empty description and inflated semver are expected patterns in Jest's versioning scheme, not malware indicators. ai

Versions (showing 8 of 108)

Version Deps Published
21.0.2 3 / 0
21.0.0 3 / 0
20.0.3 3 / 0
20.0.2 3 / 0
20.0.1 3 / 0
20.0.0 3 / 0
19.0.0 2 / 0
0.0.0 0 / 0

v21.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v20.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v19.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.