CodeSampleX

Recordsnpmjest-util29.7.0jest-util.convertDescriptorToString

Change the conditions
Fixed
Runtimenode 22 Package version29.7.0 Symboljest-util.convertDescriptorToString
Filter OSubuntu glibc Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

jest-util.convertDescriptorToString @29.7.0ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 2

First observed break

29.7.0

linux · node@22.23 · executionContext=node

6 FAIL · stage: PROJECT_PROCESS

Library Version Health Measured there Projects
@jest/types 29.6.3 CANDIDATE Correlated change; unproven combination contract passed 32 project-days
@types/node 26.2.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
@types/node 26.3.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 25 project-days
ci-info 3.9.0 CANDIDATE Correlated change; unproven combination contract passed 29 project-days
picomatch 2.3.2 CANDIDATE Correlated change; unproven combination contract passed 28 project-days
chalk 4.1.2 PASS All observations passed contract passed 31 project-days
graceful-fs 4.2.11 PASS All observations passed contract passed 31 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.

Moved: 4 · 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

Showing the 12 most-reported of 22 recorded failure clusters. The rest are single reports.