Recordscargorand0.8.8
Change the conditions
Current conditions
rand @0.8.8ubuntu glibc · x64 · cargo 1
package-level total, not an API
2 of 2 passed
Observed — real project builds reported from this coordinate.
no sample at this coordinate yet
- Project observations
- 2 / 2
- Contract verifications
- nothing at this coordinate
- Usage records
- 2
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Dependency Health
Observed combinations and failure evidence for this release
Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| rand_chacha | 0.3.1 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| rand_core | 0.6.4 | CHANGED Version changed, no linked failure | builds observed | 1 project-day |
| libc | 0.2.189 | PASS All observations passed | contract passed | 1 project-day |
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.10.2 | 0.9.5 | 0.9.1 | 0.8.8 |
|---|---|---|---|---|
| rand_chacha | — | 0.9.0 | 0.9.0 | 0.3.1 |
| rand_core | 0.10.1 | 0.9.5 | 0.9.5 | 0.6.4 |
| chacha20 | 0.10.1 | — | — | — |
| getrandom | 0.4.3 | — | — | — |
| libc | — | — | — | 0.2.189 |
Moved: 2 · unchanged at every release: 3
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.