CodeSampleX

Recordsnpm@tybys/wasm-util0.10.3@tybys/wasm-util.extendMemory

Change the conditions
Fixed
Runtimenode 22 Package version0.10.3 Symbol@tybys/wasm-util.extendMemory
Filter OSubuntu glibc Architecturex64 Package managernpm 10 Execution contextnode libcglibc Clear filters

Current conditions

@tybys/wasm-util.extendMemory @0.10.3ubuntu glibc · x64 · node 22 · npm 10 · node

0 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 failed (1)

Project observations
1 / 1
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

0.10.3

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:054c93088b95acdec26c27553355ea7447db339349572fdd4ba431478ecb744a

Library Version Health Measured there Projects
tslib 2.8.1 PASS All observations passed contract passed 2 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.

Library0.10.40.10.30.10.20.10.1
tslib 2.8.1 2.8.1 2.8.1 2.8.1

Moved: 0 · unchanged at every release: 1

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