CodeSampleX

Recordsnpm@babel/core8.0.1@babel/core.transformFileSync

Change the conditions
Fixed
Symbol@babel/core.transformFileSync Package managernpm
Filter OSalpine musl Runtimenode 22 Package version8.0.1 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

@babel/core.transformFileSync @8.0.1alpine musl · x64 · node 22 · npm · node

2 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 came back clean

Project observations
nothing at this coordinate
Contract verifications
2 / 2
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-08-18
Evidence you can open

Dependencies

LibraryVersionMeasured thereProjects
@babel/code-frame 8.0.0 contract passed 8 project-days
@babel/generator 8.0.0 contract passed 8 project-days
@babel/helper-compilation-targets 8.0.0 contract passed 5 project-days
@babel/helpers 8.0.0 contract passed 5 project-days
@babel/parser 8.0.4 contract passed 5 project-days
@babel/template 8.0.0 contract passed 5 project-days
@babel/traverse 8.0.4 contract passed 5 project-days
@babel/types 8.0.4 contract passed 5 project-days
@types/gensync 1.0.5 contract passed 5 project-days
convert-source-map 2.0.0 contract passed 7 project-days
empathic 2.0.1 contract passed 5 project-days
gensync 1.0.0-beta.2 contract passed 7 project-days
import-meta-resolve 4.2.0 contract passed 5 project-days
json5 2.2.3 contract passed 7 project-days
obug 2.1.4 contract passed 5 project-days
semver 7.8.5 contract passed 5 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.

Recent failure clusters