CodeSampleX

Recordscargohyper1.11.0

Change the conditions
Filter OSalpine musl Runtimerust 1 Package version1.11.0 Symbolwhole package Architecturex64 Package managercargo Execution contextrust libcmusl

Current conditions

hyper @1.11.0alpine 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 (2)

Project observations
nothing at this coordinate
Contract verifications
nothing at this coordinate
Usage records
2
Independent reporting peers
1
Last recorded
2026-09-15
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Changed 1 · Unknown 3 · Steady 9

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

Library Version Health Measured there Projects
smallvec 1.15.2 CHANGED Version changed, no linked failure nothing measured 7 project-days
atomic-waker 1.1.2 UNKNOWN No linked outcome measured nothing measured 6 project-days
httparse 1.10.1 UNKNOWN No linked outcome measured nothing measured 6 project-days
httpdate 1.0.3 UNKNOWN No linked outcome measured nothing measured 2 project-days
bytes 1.12.1 PASS All observations passed contract passed 12 project-days
futures-channel 0.3.34 PASS All observations passed builds observed 6 project-days
futures-core 0.3.34 PASS All observations passed contract passed 8 project-days
http 1.5.0 PASS All observations passed contract passed 12 project-days
http-body 1.1.0 PASS All observations passed contract passed 12 project-days
itoa 1.0.18 PASS All observations passed contract passed 8 project-days
pin-project-lite 0.2.17 PASS All observations passed contract passed 8 project-days
tokio 1.53.1 PASS All observations passed contract passed 10 project-days
want 0.3.1 PASS All observations passed builds observed 4 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.11.11.11.0
smallvec 1.16.1 1.15.2
atomic-waker 1.1.2 1.1.2
bytes 1.12.1 1.12.1
futures-channel 0.3.34 0.3.34
futures-core 0.3.34 0.3.34
h2 0.4.19 —
http 1.5.0 1.5.0
http-body 1.1.0 1.1.0
httparse 1.10.1 1.10.1
httpdate 1.0.3 1.0.3
itoa 1.0.18 1.0.18
pin-project-lite 0.2.17 0.2.17
tokio 1.53.1 1.53.1
want 0.3.1 0.3.1

Moved: 1 · unchanged at every release: 13

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.