CodeSampleX

Recordsnpmjest-watcher29.7.0jest-watcher.KEYS

Change the conditions
Fixed
Symboljest-watcher.KEYS Package managernpm
Filter OSdebian glibc Runtimenode 22 Package version29.7.0 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

jest-watcher.KEYS @29.7.0debian glibc · x64 · node 22 · npm · node

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 4

First observed break

29.7.0

windows · node@24.13 · moduleSystem=cjs · executionContext=node

5 FAIL · stage: PROJECT_PROCESS

View exact conditions View failure cluster
Library Version Health Measured there Projects
@jest/test-result 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
@jest/types 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
@types/node 26.2.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
@types/node 26.4.0 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@types/node 26.4.1 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
jest-util 29.7.0 CANDIDATE Correlated change; unproven combination contract passed 14 project-days
ansi-escapes 4.3.2 PASS All observations passed contract passed 14 project-days
chalk 4.1.2 PASS All observations passed contract passed 14 project-days
emittery 0.13.1 PASS All observations passed contract passed 13 project-days
string-length 4.0.2 PASS All observations passed contract passed 14 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/test-result 30.4.1 29.7.0
@jest/types 30.4.1 29.6.3
@types/node 26.4.0 26.2.0
jest-util 30.4.1 29.7.0
ansi-escapes 4.3.2 4.3.2
chalk 4.1.2 4.1.2
emittery 0.13.1 0.13.1
string-length 4.0.2 4.0.2

Moved: 4 · unchanged at every release: 4

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