CodeSampleX

Recordscargojs-sys0.3.104js_sys::Boolean

Change the conditions
Fixed
Symboljs_sys::Boolean
Filter OSubuntu glibc Package version0.3.104 Architecturex64 Package managercargo 1 libcglibc Clear filters

Current conditions

js_sys::Boolean @0.3.104ubuntu glibc · x64 · cargo 1

0 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 failed

Project observations
nothing at this coordinate
Contract verifications
0 / 1
Last recorded
2026-09-19

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

0.3.104

linux

1 FAIL · stage: UNKNOWN · fingerprint: sha256:5650faa5dc98fd1ed4484103a0a7200aa4d95d21671f3c637407bb992fe7c5d1

Library Version Health Measured there Projects
cfg-if 1.0.4 CANDIDATE Correlated change; unproven combination contract passed 4 project-days
cfg-if 1.0.5 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
wasm-bindgen 0.2.127 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
futures-util 0.3.34 PASS All observations passed contract passed 10 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: 2 · 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