CodeSampleX

Recordsnpm@emnapi/wasi-threads1.2.2

Change the conditions
Fixed
OSdebian glibc Package version1.2.2
Filter Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode libcglibc Clear filters

Current conditions

@emnapi/wasi-threads @1.2.2debian glibc · x64 · node 22 · npm · node

package-level total, not an API

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
4 / 4
Contract verifications
1 / 1
Usage records
4
Independent reporting peers
1
Last recorded
2026-10-13
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Steady 1

First observed break

1.2.2

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

1 FAIL · stage: UNKNOWN · fingerprint: sha256:88af852f99a8104e4bc3c23eea27ebf2990625ccabf45313970f5fd7fe56c4e2

View exact conditions View failure cluster
Library Version Health Measured there Projects
tslib 2.8.1 PASS All observations passed contract passed 7 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.

Library1.2.31.2.21.2.11.1.0
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