Recordscargorand_core0.9.5rand_core
Change the conditions
Current conditions
rand_core @0.9.5alpine 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-14
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.9.5
linux
1 FAIL
· stage: UNKNOWN
· fingerprint: sha256:ece5e236c454a3b87228df98270b04a491c4374776b4ed3ee8e5b0d25d940c63
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| getrandom | 0.3.4 | CANDIDATE Correlated change; unproven combination | contract passed | 12 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: 0
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 exit 101 Evidence gap ×1 0.9.5 os=linux rand_core sha256:ece5e236c454…Compiling rand_core v0.9.5 · Compiling sample-rand-core v1.0.0 (<path> · warning: variable does not need to be mutable · --> test/contract.rs:<n>:<n>cargo · unclassified-diagnostic · outer cargo run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-13 · Last seen: 2026-10-13Diagnostic re-verification candidate