CodeSampleX

Recordsnpm@babel/traverse7.29.7@babel/traverse.default

Change the conditions
Fixed
OSdebian glibc Symbol@babel/traverse.default Package managernpm
Filter Runtimenode 22 Package version7.29.7 Architecturex64 Execution contextnode libcglibc Clear filters

Current conditions

@babel/traverse.default @7.29.7debian 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 9 · Steady 1

First observed break

7.29.7

windows · executionContext=node

5 FAIL · stage: PROJECT_TEST

View exact conditions View failure cluster
Library Version Health Measured there Projects
@babel/code-frame 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@babel/generator 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@babel/generator 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@babel/helper-globals 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
@babel/parser 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
@babel/parser 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@babel/template 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@babel/types 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
@babel/types 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
debug 4.4.3 PASS All observations passed contract passed 5 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.

Library8.0.47.29.87.29.77.28.5
@babel/code-frame 8.0.0 7.29.7 7.29.7 7.27.1
@babel/generator 8.0.0 7.29.8 7.29.8 7.28.5
@babel/helper-globals 8.0.0 7.29.7 7.29.7 7.28.0
@babel/parser 8.0.4 7.29.8 7.29.8 7.28.5
@babel/template 8.0.0 7.29.7 7.29.7 7.27.2
@babel/types 8.0.4 7.29.8 7.29.8 7.28.5
debug — 4.4.3 4.4.3 4.4.3
obug 2.1.4 — — —

Moved: 6 · 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.