Recordscargofutures-util
Change the conditions
Current conditions
futures-util @0.3.31linux · musl · x64 · rust 1 · cargo · rust
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
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
alpine musl · x64 · rust 1 · cargo · rust
3 of 3 passed
Verified — this network ran a contract at this coordinate.
-
futures_util::stream::FuturesOrderedalpine musl · x64 · rust 1 · cargo · rust
3 of 3 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
All 4 dependencies report steady passing evidence.
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| pin-utils | 0.1.0 | UNKNOWN No linked outcome measured | nothing measured | 1 project-day |
| futures-core | 0.3.34 | PASS All observations passed | contract passed | 1 project-day |
| futures-sink | 0.3.34 | PASS All observations passed | contract passed | 1 project-day |
| futures-task | 0.3.34 | PASS All observations passed | contract passed | 1 project-day |
| pin-project-lite | 0.2.17 | 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.
| Library | 0.3.34 | 0.3.31 |
|---|---|---|
| futures-core | 0.3.34 | 0.3.34 |
| futures-io | 0.3.34 | — |
| futures-macro | 0.3.34 | — |
| futures-sink | 0.3.34 | 0.3.34 |
| futures-task | 0.3.34 | 0.3.34 |
| memchr | 2.8.3 | — |
| pin-project-lite | 0.2.17 | 0.2.17 |
| pin-utils | — | 0.1.0 |
| slab | 0.4.12 | — |
| tokio | 1.53.1 | — |
| tower | 0.5.3 | — |
| tower-layer | 0.3.3 | — |
| tower-service | 0.3.3 | — |
Moved: 0 · 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.