CodeSampleX

Recordscargowasm-bindgen-macro

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

Current conditions

wasm-bindgen-macro @0.2.127alpine musl · x64 · rust 1 · cargo · rust

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
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 1 · Steady 1

First observed break

0.2.127

linux

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

Library Version Health Measured there Projects
wasm-bindgen-macro-support 0.2.127 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
quote 1.0.47 PASS All observations passed contract passed 17 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: 1 · unchanged at every release: 1

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.