CodeSampleX

Recordscargoh20.4.20

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

Current conditions

h2 @0.4.20alpine 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-10-19

Dependency Health

Observed combinations and failure evidence for this release

Changed 2 · Steady 9

Dependency changes observed: 2. No failure evidence is linked to these resolved trees yet.

Library Version Health Measured there Projects
tokio 1.54.0 CHANGED Version changed, no linked failure builds observed 2 project-days
tokio-util 0.7.20 CHANGED Version changed, no linked failure builds observed 2 project-days
atomic-waker 1.1.2 PASS All observations passed builds observed 2 project-days
bytes 1.12.1 PASS All observations passed contract passed 2 project-days
fnv 1.0.7 PASS All observations passed builds observed 2 project-days
futures-core 0.3.34 PASS All observations passed contract passed 2 project-days
futures-sink 0.3.34 PASS All observations passed contract passed 2 project-days
http 1.5.0 PASS All observations passed contract passed 2 project-days
indexmap 2.14.2 PASS All observations passed builds observed 2 project-days
slab 0.4.12 PASS All observations passed contract passed 2 project-days
tracing 0.1.44 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.

Moved: 2 · unchanged at every release: 9

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.