CodeSampleX

Recordsnpm@jest/test-result29.7.0

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

Current conditions

@jest/test-result @29.7.0ubuntu 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 (1)

Project observations
19 / 19
Contract verifications
0 / 3
Usage records
2
Independent reporting peers
3
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 2

First observed break

29.7.0

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:83bb774d036676c6450400f533510c87165d7879e817977fb7245a5acef3dd9f

View exact conditions View failure cluster
Library Version Health Measured there Projects
@jest/console 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
@jest/types 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 16 project-days
@types/istanbul-lib-coverage 2.0.6 PASS All observations passed contract passed 13 project-days
collect-v8-coverage 1.0.3 PASS All observations passed contract passed 13 project-days

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.

Library30.4.129.7.0
@jest/console 30.4.1 29.7.0
@jest/types 30.4.1 29.6.3
@types/istanbul-lib-coverage 2.0.6 2.0.6
collect-v8-coverage 1.0.3 1.0.3

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