CodeSampleX

Recordsnpm@babel/traverse

Change the conditions
Fixed
OSubuntu glibc Package version8.0.4 Execution contextnode
Filter Runtimenode 22 Architecturex64 Package managernpm 10 libcglibc Clear filters

Current conditions

@babel/traverse @8.0.4ubuntu glibc · x64 · node 22 · npm 10 · node

0 of 13 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
95 / 96
Contract verifications
0 / 13
Usage records
29
Independent reporting peers
3
Last recorded
2026-09-05

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 1

First observed break

8.0.4

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

6 FAIL · stage: UNKNOWN · fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2

Library Version Health Measured there Projects
@babel/code-frame 8.0.0 CANDIDATE Correlated change; unproven combination contract passed 40 project-days
@babel/generator 8.0.0 CANDIDATE Correlated change; unproven combination contract passed 40 project-days
@babel/helper-globals 8.0.0 CANDIDATE Correlated change; unproven combination contract passed 37 project-days
@babel/parser 8.0.4 CANDIDATE Correlated change; unproven combination contract passed 40 project-days
@babel/template 8.0.0 CANDIDATE Correlated change; unproven combination contract passed 40 project-days
@babel/types 8.0.4 CANDIDATE Correlated change; unproven combination contract passed 41 project-days
obug 2.1.4 PASS All observations passed contract passed 39 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: 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.