CodeSampleX

Recordscargorand_core0.9.5rand_core

Change the conditions
Fixed
Symbolrand_core Package managercargo
Filter OSalpine musl Runtimerust 1 Package version0.9.5 Architecturex64 Execution contextrust libcmusl Clear filters

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

Observed problems 1 · Changed 1 · Steady 0

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.

Library0.9.50.6.4
getrandom 0.3.4 0.2.17

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