CodeSampleX

Recordscargomio1.2.5

Change the conditions
Fixed
Package version1.2.5 Package managercargo
Filter OSalpine musl Runtimerust 1 Symbolwhole package Architecturex64 Execution contextrust libcmusl Clear filters

Current conditions

mio @1.2.5alpine musl · x64 · rust 1 · cargo · rust

package-level total, not an API

Recorded as present in projects. Nothing was run at this coordinate.

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
1
Independent reporting peers
1
Last recorded
2026-11-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 1 · Steady 2

First observed break

1.2.5

linux

2 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:0479254218ac3780b34745e946705b5f6ea072bc45cc7771f5a9b6fbfb5955e8

Library Version Health Measured there Projects
libc 0.2.191 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
wasi 0.11.1+wasi-snapshot-preview1 PASS All observations passed contract passed 8 project-days
windows-sys 0.61.2 PASS All observations passed contract passed 8 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: 2 · unchanged at every release: 2

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