CodeSampleX

Recordscargowasm-bindgen-macro-support

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package version0.2.130

No recorded evidence matches these filters. Nothing is inferred; clear a filter to widen the slice.

Dependency Health

Observed combinations and failure evidence for this release

Changed 3 · Steady 2

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

Library Version Health Measured there Projects
bumpalo 3.20.4 CHANGED Version changed, no linked failure builds observed 2 project-days
syn 3.0.10 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
proc-macro2 1.0.107 PASS All observations passed contract passed 2 project-days
quote 1.0.47 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.