CodeSampleX

Recordsnpm@babel/helper-skip-transparent-expression-wrappers8.0.0

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

Current conditions

@babel/helper-skip-transparent-expression-wrappers @8.0.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 4 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
7 / 7
Contract verifications
0 / 4
Independent reporting peers
1
Last recorded
2026-09-03

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 2 · Steady 0

First observed break

8.0.0 @babel/traverse@8.0.4

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:455451e1a14e249427c2bc1772777b41d7ea0e8c07e3fe88a46ec6adb3bc054e

Library Version Health Measured there Projects
@babel/traverse 8.0.4 FAIL Linked failure observed; version changed across releases contract passed 7 project-days
@babel/types 8.0.4 FAIL Linked failure observed; version changed across releases contract passed 6 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.07.29.7
@babel/traverse 8.0.4 7.29.8
@babel/types 8.0.4 7.29.8

Moved: 2 · unchanged at every release: 0

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