CodeSampleX

Recordsnpm@webassemblyjs/wasm-edit1.14.1edit

Change the conditions
Fixed
Symboledit Package managernpm
Filter OSalpine musl Runtimenode 22 Package version1.14.1 Architecturex64 Execution contextnode libcmusl Clear filters

Current conditions

edit @1.14.1alpine musl · x64 · node 22 · npm · node

1 of 1 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 (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-27
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 8

First observed break

1.14.1

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

4 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2

View exact conditions View failure cluster
Library Version Health Measured there Projects
@webassemblyjs/ast 1.14.1 PASS All observations passed contract passed 4 project-days
@webassemblyjs/helper-buffer 1.14.1 PASS All observations passed contract passed 3 project-days
@webassemblyjs/helper-wasm-bytecode 1.13.2 PASS All observations passed contract passed 3 project-days
@webassemblyjs/helper-wasm-section 1.14.1 PASS All observations passed contract passed 3 project-days
@webassemblyjs/wasm-gen 1.14.1 PASS All observations passed contract passed 3 project-days
@webassemblyjs/wasm-opt 1.14.1 PASS All observations passed contract passed 3 project-days
@webassemblyjs/wasm-parser 1.14.1 PASS All observations passed contract passed 4 project-days
@webassemblyjs/wast-printer 1.14.1 PASS All observations passed contract passed 3 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