CodeSampleX

Recordsnpm@babel/parser7.29.7

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

Current conditions

@babel/parser @7.29.7windows 11 · 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 (1)

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 2 · Steady 0

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/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 1 project-day

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/types 8.0.4 7.29.8 7.29.8 7.28.5

Moved: 1 · 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