CodeSampleX

Recordscargowasm-bindgen-shared0.2.128

Change the conditions
Fixed
Package version0.2.128 Package managercargo
Filter OSalpine musl Runtimerust 1 Symbolwhole package Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

wasm-bindgen-shared @0.2.128alpine musl · x64 · rust 1 · cargo · rust

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-11-08

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

0.2.128

linux

2 FAIL · stage: UNKNOWN · fingerprint: sha256:8f78f52362b82ea5b9bccb44e43e55e6632841a2a7d15e6ac5d5cc8ec82bc020

Library Version Health Measured there Projects
unicode-ident 1.0.26 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
unicode-ident 1.0.27 CANDIDATE Correlated change; unproven combination contract passed 23 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.2.1300.2.1290.2.1280.2.127
unicode-ident 1.0.27 1.0.27 1.0.26 1.0.27

Moved: 1 · unchanged at every release: 0

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