CodeSampleX

Recordsnpm@babel/generator7.29.7

Change the conditions
Fixed
OSwindows Package version7.29.7 Package managernpm 11
Filter Runtimenode 24 Symbolwhole package Architecturex64 Execution contextnode Clear filters

Current conditions

@babel/generator @7.29.7windows · x64 · node 24 · npm 11 · node

package-level total, not an API

0 of 11 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate failed (5)

Project observations
25 / 28
Contract verifications
0 / 11
Usage records
48
Independent reporting peers
1
Failures with a captured fingerprint
1 / 3
Last recorded
2026-09-15
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 3

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/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 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 7 project-days
@jridgewell/gen-mapping 0.3.13 PASS All observations passed contract passed 9 project-days
@jridgewell/trace-mapping 0.3.31 PASS All observations passed contract passed 10 project-days
jsesc 3.1.0 PASS All observations passed contract passed 9 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.87.29.77.28.5
@babel/parser 8.0.4 7.29.8 7.29.7 7.28.5
@babel/types 8.0.4 7.29.8 7.29.7 7.28.5
@jridgewell/gen-mapping 0.3.13 0.3.13 0.3.13 0.3.13
@jridgewell/trace-mapping 0.3.31 0.3.31 0.3.31 0.3.31
@types/jsesc 2.5.1 — — —
jsesc 3.1.0 3.1.0 3.1.0 3.1.0

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