CodeSampleX

Recordscargogetrandom0.2.17getrandom::register_custom_getrandom

Change the conditions
Fixed
OSlinux Symbolgetrandom::register_custom_getrandom
Filter Runtimerust 1 Package version0.2.17 Architecturex64 Package managercargo Execution contextrust libcmusl Clear filters

Current conditions

getrandom::register_custom_getrandom @0.2.17linux · 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
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 4 · Steady 3

First observed break

0.2.17

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:581c58c1c7ac1c174300ebe7fe6f6efcea19fe2db06561b3fdd49b3747eccc95

Library Version Health Measured there Projects
cfg-if 1.0.4 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
cfg-if 1.0.5 CANDIDATE Correlated change; unproven combination contract passed 13 project-days
libc 0.2.189 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
libc 0.2.190 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
js-sys 0.3.104 PASS All observations passed contract passed 2 project-days
wasi 0.11.1+wasi-snapshot-preview1 PASS All observations passed contract passed 24 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.

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