CodeSampleX

Recordscargotower0.4.13

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

Current conditions

tower @0.4.13alpine musl · x64 · rust 1 · cargo · rust

package-level total, not an API

3 of 3 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
6 / 6
Contract verifications
3 / 3
Usage records
4
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-08

Dependency Health

Observed combinations and failure evidence for this release

Steady 7

All 7 dependencies report steady passing evidence.

Library Version Health Measured there Projects
futures-core 0.3.34 PASS All observations passed contract passed 1 project-day
futures-util 0.3.34 PASS All observations passed contract passed 1 project-day
pin-project 1.1.13 PASS All observations passed builds observed 1 project-day
pin-project-lite 0.2.17 PASS All observations passed contract passed 1 project-day
tower-layer 0.3.3 PASS All observations passed contract passed 1 project-day
tower-service 0.3.3 PASS All observations passed contract passed 1 project-day
tracing 0.1.44 PASS All observations passed contract passed 1 project-day

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: 0 · unchanged at every release: 10

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.