CodeSampleX

Recordsnpm@babel/helper-wrap-function8.0.0

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

Current conditions

@babel/helper-wrap-function @8.0.0ubuntu glibc · x64 · node 22 · npm 10 · node

package-level total, not an API

0 of 2 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 / 2
Independent reporting peers
1
Last recorded
2026-09-05
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

8.0.0

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:c713e7987e7b3bfb480a2e7903c4bad1da7774d32c561f19a6351940fd8c07ff

View exact conditions View failure cluster
Library Version Health Measured there Projects
@babel/template 8.0.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
@babel/traverse 8.0.4 CANDIDATE Correlated change; unproven combination contract passed 7 project-days
@babel/types 8.0.4 CANDIDATE Correlated change; unproven combination contract passed 7 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/template 8.0.0 7.29.7
@babel/traverse 8.0.4 7.29.8
@babel/types 8.0.4 7.29.8

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