CodeSampleX

Recordscargowasm-bindgen0.2.130

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

Current conditions

wasm-bindgen @0.2.130ubuntu glibc · x64 · cargo 1

package-level total, not an API

2 of 2 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
2 / 2
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-11-21

Dependency Health

Observed combinations and failure evidence for this release

Changed 3 · Steady 1

Dependency changes observed: 3. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
cfg-if 1.0.5 CHANGED Version changed, no linked failure contract passed 2 project-days
wasm-bindgen-macro 0.2.130 CHANGED Version changed, no linked failure builds observed 2 project-days
wasm-bindgen-shared 0.2.130 CHANGED Version changed, no linked failure builds observed 2 project-days
rustversion 1.0.23 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.

Moved: 3 · 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.