CodeSampleX

Recordsnpm@jest/test-result30.4.1

Change the conditions
Fixed
Package version30.4.1
Filter OSubuntu glibc Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@jest/test-result @30.4.1ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 3 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed

Project observations
6 / 6
Contract verifications
0 / 3
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

30.4.1

linux · node@22.23 · moduleSystem=cjs · executionContext=node

1 FAIL · stage: UNKNOWN · fingerprint: sha256:769e5b50934127934638762c5a14e135fd136d8f7f1621708b52dce382c93529

Library Version Health Measured there Projects
@jest/console 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@jest/types 30.4.1 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@types/istanbul-lib-coverage 2.0.6 PASS All observations passed contract passed 1 project-day
collect-v8-coverage 1.0.3 PASS All observations passed contract passed 1 project-day

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

Dependency versions across releases

What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.

Moved: 2 · unchanged at every release: 2

An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.

Recent failure clusters