CodeSampleX

Recordsnpm@webassemblyjs/wast-parser1.14.1@webassemblyjs/wast-parser.parse32I

Change the conditions
Fixed
Symbol@webassemblyjs/wast-parser.parse32I
Filter OSdebian glibc Runtimenode 22 Package version1.14.1 Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@webassemblyjs/wast-parser.parse32I @1.14.1debian glibc · 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
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 6

First observed break

1.14.1

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

2 FAIL · stage: UNKNOWN · fingerprint: sha256:3b3190f2cd44c327e0d62d5fcac6e314a022dc126a98b5c1b38661e44ab6a020

Library Version Health Measured there Projects
@webassemblyjs/ast 1.14.1 PASS All observations passed contract passed 8 project-days
@webassemblyjs/floating-point-hex-parser 1.13.2 PASS All observations passed contract passed 8 project-days
@webassemblyjs/helper-api-error 1.13.2 PASS All observations passed contract passed 8 project-days
@webassemblyjs/helper-code-frame 1.14.1 PASS All observations passed contract passed 8 project-days
@webassemblyjs/helper-fsm 1.13.2 PASS All observations passed contract passed 8 project-days
@xtuc/long 4.2.2 PASS All observations passed contract passed 8 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