Recordscargogetrandom0.4.3getrandom::fill_uninit
Change the conditions
Current conditions
getrandom::fill_uninit @0.4.3linux · 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
- 2 / 2
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-10-13
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.4.3
linux
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:2304c1c3b479cc4657d40ed18c0ff7e3b7dc68dc505b2fcea363ecce1c793ae9
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| cfg-if | 1.0.4 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| cfg-if | 1.0.5 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| libc | 0.2.189 | CANDIDATE Correlated change; unproven combination | contract passed | 8 project-days |
| libc | 0.2.191 | CANDIDATE Correlated change; unproven combination | contract passed | 6 project-days |
| r-efi | 6.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| rand_core | 0.10.1 | UNKNOWN No linked outcome measured | nothing measured | 3 project-days |
| js-sys | 0.3.104 | PASS All observations passed | contract passed | 2 project-days |
| wasm-bindgen | 0.2.127 | 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.
| Library | 0.4.3 | 0.3.4 | 0.2.17 |
|---|---|---|---|
| cfg-if | 1.0.4 | 1.0.5 | 1.0.4 |
| libc | 0.2.191 | 0.2.190 | 0.2.190 |
| r-efi | 6.0.0 | 5.3.0 | — |
| js-sys | 0.3.104 | — | 0.3.104 |
| rand_core | 0.10.1 | — | — |
| wasi | — | — | 0.11.1+wasi-snapshot-preview1 |
| wasip2 | — | 1.0.4+wasi-0.2.12 | — |
| wasm-bindgen | 0.2.127 | — | 0.2.127 |
Moved: 3 · unchanged at every release: 5
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 PROJECT_COMPILE exit 101 E0599 ×1 0.4.3 os=linux sha256:2304c1c3b479…error[E0599]: no method named `release` found for struct `Client` in the current scoperust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-01 · Last seen: 2026-11-01
-
observed PROJECT_COMPILE exit 101 ×1 0.4.3 os=linux sha256:a14c14f9b8da…error: could not compile `sample` (bin <str>) due to 2 previous errorsrust/rustc · compiler-diagnostic · outer cargo runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-11-01 · Last seen: 2026-11-01