CodeSampleX

Recordsnpm@babel/traverse7.29.8

Change the conditions
Fixed
Runtimenode 22 Package managerpnpm 10 Execution contextnode
Filter OSwindows 11 Package version7.29.8 Symbolwhole package Architecturex64 Clear filters

Current conditions

@babel/traverse @7.29.8windows 11 · x64 · node 22 · pnpm 10 · node

package-level total, not an API

11 of 14 passed

Observed — real project builds reported from this coordinate.

there is a sample here, and nothing of ours has run it at this coordinate yet (1)

Project observations
11 / 14
Contract verifications
nothing at this coordinate
Usage records
72
Independent reporting peers
1
Failures with a captured fingerprint
0 / 3
Last recorded
2026-08-21
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 1

First observed break

7.29.8

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

32 FAIL · stage: UNKNOWN · fingerprint: sha256:9f91c975308128a0f4f23e33b9d5936b9c39535b5c01aa9245b8cdc4b0a37a10

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 159 project-days
@babel/generator 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 159 project-days
@babel/helper-globals 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 145 project-days
@babel/parser 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 160 project-days
@babel/template 7.29.7 CANDIDATE Correlated change; unproven combination contract passed 160 project-days
@babel/types 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 161 project-days
debug 4.4.3 PASS All observations passed contract passed 158 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.

Recent failure clusters