Recordscargomio1.2.2
Change the conditions
Current conditions
mio @1.2.2alpine 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.
there is a sample here, and nothing of ours has run it at this coordinate yet (1)
- Project observations
- nothing at this coordinate
- Contract verifications
- nothing at this coordinate
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-08
Dependency Health
Observed combinations and failure evidence for this release
All 4 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| libc | 0.2.189 | PASS All observations passed | contract passed | 9 project-days |
| log | 0.4.34 | PASS All observations passed | builds observed | 1 project-day |
| wasi | 0.11.1+wasi-snapshot-preview1 | PASS All observations passed | contract passed | 9 project-days |
| windows-sys | 0.61.2 | PASS All observations passed | contract passed | 9 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.
| Library | 1.2.3 | 1.2.2 |
|---|---|---|
| libc | 0.2.189 | 0.2.189 |
| log | — | 0.4.34 |
| wasi | 0.11.1+wasi-snapshot-preview1 | 0.11.1+wasi-snapshot-preview1 |
| windows-sys | 0.61.2 | 0.61.2 |
Moved: 0 · unchanged at every release: 4
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.