CodeSampleX

Recordsnpm@babel/generator7.29.8

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

Current conditions

@babel/generator @7.29.8ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 61 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
330 / 338
Contract verifications
0 / 61
Usage records
78
Independent reporting peers
3
Failures with a captured fingerprint
0 / 8
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 3

First observed break

7.29.8

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

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

Library Version Health Measured there Projects
@babel/parser 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 160 project-days
@babel/types 7.29.8 CANDIDATE Correlated change; unproven combination contract passed 160 project-days
@jridgewell/gen-mapping 0.3.13 PASS All observations passed contract passed 151 project-days
@jridgewell/trace-mapping 0.3.31 PASS All observations passed contract passed 151 project-days
jsesc 3.1.0 PASS All observations passed contract passed 147 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: 2 · unchanged at every release: 4

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 46 recorded failure clusters. The rest are single reports.