Recordsnpm@webassemblyjs/wasm-opt
Change the conditions
Current conditions
shrinkPaddedLEB128 @1.14.1x64 · node 22 · node
1 of 3 passed
Verified — this network ran a contract at this coordinate.
there is a sample here, and this coordinate records both a passing and a failing run of it (1)
- Project observations
- 5 / 5
- Contract verifications
- 1 / 3
- Independent reporting peers
- 2
- Last recorded
- 2026-08-31
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · node 22 · npm · node
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · node 22 · npm 10 · node
0 of 2 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
1.14.1
windows · node@24.13 · moduleSystem=cjs · executionContext=node
4 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:0470f88d95bb52932e5704cdc30cfcecbd43ae71af54d4c5f93d16aa27317cd2
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| @webassemblyjs/ast | 1.14.1 | PASS All observations passed | contract passed | 5 project-days |
| @webassemblyjs/helper-buffer | 1.14.1 | PASS All observations passed | contract passed | 5 project-days |
| @webassemblyjs/wasm-gen | 1.14.1 | PASS All observations passed | contract passed | 5 project-days |
| @webassemblyjs/wasm-parser | 1.14.1 | PASS All observations passed | 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.