Recordscargowasm-bindgen-macro0.2.128
Change the conditions
Current conditions
wasm-bindgen-macro @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
- 3
- Independent reporting peers
- 1
- Last recorded
- 2026-11-08
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.2.128
linux
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:034c59ed23d6ae804f13470a52f0aced0db2d18a608b966c0ddf6ac7517ac187
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| wasm-bindgen-macro-support | 0.2.128 | CANDIDATE Correlated change; unproven combination | contract passed | 15 project-days |
| quote | 1.0.47 | PASS All observations passed | contract passed | 15 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.
| Library | 0.2.130 | 0.2.129 | 0.2.128 | 0.2.127 |
|---|---|---|---|---|
| wasm-bindgen-macro-support | 0.2.130 | 0.2.129 | 0.2.128 | 0.2.127 |
| quote | 1.0.47 | 1.0.47 | 1.0.47 | 1.0.47 |
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.
Recent failure clusters
-
observed UNKNOWN signal ABORTED Evidence gap ×1 0.2.128 os=linux sha256:034c59ed23d6…Compiling sample-wasm-bindgen v0.1.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.19s …cargo · unclassified-diagnostic · outer cargo run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17Diagnostic re-verification candidate
-
observed UNKNOWN exit 101 Evidence gap ×1 0.2.128 os=linux sha256:49fbc1f03025…Compiling sample-wasm-bindgen v0.1.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.33s …cargo · unclassified-diagnostic · outer cargo run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17Diagnostic re-verification candidate
-
observed UNKNOWN exit 101 Evidence gap ×1 0.2.128 os=linux sha256:ce88fa682bac…Updating crates.io index · Locking 12 packages to latest compatible versions · Adding wasm-bindgen v0.2.128 (available: v0.2.129) …cargo · unclassified-diagnostic · outer cargo run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17Diagnostic re-verification candidate
-
observed UNKNOWN exit 101 Evidence gap ×1 0.2.128 os=linux sha256:d5ef89c0ce65…Compiling sample-wasm-bindgen v0.1.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.25s …cargo · unclassified-diagnostic · outer cargo run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17Diagnostic re-verification candidate
-
observed UNKNOWN exit 101 Evidence gap ×1 0.2.128 os=linux sha256:e0ded99321af…Compiling sample-wasm-bindgen v0.1.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.46s …cargo · unclassified-diagnostic · outer cargo run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17Diagnostic re-verification candidate