Recordscargofutures-util
Change the conditions
Current conditions
futures-util @0.3.33alpine musl · x64 · rust 1 · cargo · rust
1 of 1 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
- 2 / 2
- Contract verifications
- 1 / 1
- Usage records
- 1
- Independent reporting peers
- 1
- Last recorded
- 2026-08-30
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
futures_util::io::AsyncBufReadExt::read_line
1 of 1 passed
Verified — this network ran a contract at this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
0.3.34
linux
2 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:6e60e3f6eb26664d5662a05cfa1507a242e153aff9a610daf73b87c807b302b7
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.