CodeSampleX

Recordsnpm@napi-rs/wasm-runtime1.2.3

Change the conditions
Fixed
Package version1.2.3 libcmusl
Filter OSalpine musl Runtimenode 22 Symbolwhole package Architecturex64 Package managernpm Execution contextnode Clear filters

Current conditions

@napi-rs/wasm-runtime @1.2.3alpine musl · 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
2 / 2
Contract verifications
1 / 1
Usage records
1
Independent reporting peers
1
Last recorded
2026-08-30
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 0

First observed break

1.2.3

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

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

View exact conditions View failure cluster
Library Version Health Measured there Projects
@tybys/wasm-util 0.10.3 CANDIDATE Correlated change; unproven combination 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.

Library1.2.31.1.40.2.12
@tybys/wasm-util 0.10.3 0.10.4 0.10.1
@emnapi/core — — 1.7.1
@emnapi/runtime — — 1.7.1

Moved: 1 · unchanged at every release: 2

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