CodeSampleX

Recordscargowasm-bindgen-shared

Change the conditions
Fixed
Package version0.2.127 Package managercargo 1
Filter OSubuntu glibc Architecturex64 libcglibc Clear filters

Current conditions

wasm-bindgen-shared @0.2.127ubuntu glibc · x64 · cargo 1

0 of 5 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
40 / 63
Contract verifications
0 / 5
Independent reporting peers
1
Last recorded
2026-10-22

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

0.2.127

linux

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:8d7d824b0493fa53def8924123f6771803f5ab03734b87a1ccf1c43e38a04949

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