CodeSampleX

Recordscargomio1.2.3

Change the conditions
Fixed
Package version1.2.3 Package managercargo 1
Filter OSubuntu glibc Symbolwhole package Architecturex64 libcglibc Clear filters

Current conditions

mio @1.2.3ubuntu glibc · x64 · cargo 1

package-level total, not an API

6 of 8 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
6 / 8
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-19
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

1.2.3

linux

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:689d8da7053d77d03eb6eefe30c2e8ca0f3bb13fc22a27297ce56a2f1e9fc82f

View exact conditions View failure cluster
Library Version Health Measured there Projects
libc 0.2.189 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
wasi 0.11.1+wasi-snapshot-preview1 PASS All observations passed contract passed 2 project-days
windows-sys 0.61.2 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.

Library1.2.41.2.31.2.2
libc 0.2.191 0.2.189 0.2.190
log — — 0.4.34
wasi 0.11.1+wasi-snapshot-preview1 0.11.1+wasi-snapshot-preview1 0.11.1+wasi-snapshot-preview1
windows-sys 0.61.2 0.61.2 0.61.2

Moved: 1 · 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.

Recent failure clusters