Decision Workspace
tcp-stream vs mio vs tokio
Side-by-side comparison of Rust crates
61
tcp-stream
growingv0.34.14
std::net::TcpStream on steroids
76
mio
stablev1.2.4
Lightweight non-blocking I/O.
76
tokio
stablev1.53.2
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Core Metrics
| tcp-stream | mio | tokio | |
|---|---|---|---|
| Health Score | 61 | 76 | 76 |
| Total Downloads | 13.0M | 1.1B | 1.0B |
| 30d Downloads | 0 | 0 | 0 |
| Dependents | 225 | 7.5K | 1.1M |
| Releases | 112 | 81 | 197 |
| Last Updated | 139d ago | 6d ago | 6d ago |
| Age | 7y 4m | 11y 11m | 10y 3m |
Health Breakdown
tcp-stream
Maintenance
12
Quality
14
Community
12
Popularity
8
Documentation
15
mio
Maintenance
20
Quality
17
Community
19
Popularity
8
Documentation
12
tokio
Maintenance
19
Quality
17
Community
20
Popularity
8
Documentation
12
Technical Details
| tcp-stream | mio | tokio | |
|---|---|---|---|
| Version | 0.34.14 | 1.2.4 | 1.53.2 |
| Stable (≥1.0) | ✗ No | ✓ Yes | ✓ Yes |
| License | BSD-2-Clause | MIT | MIT |
| Dependencies | 10 | 6 | 36 |
| Crate Size | 31KB | 110KB | 928KB |
| Features | 17 | 4 | 17 |
| Yanked % | 8.9% | 9.9% | 2.5% |
| Edition | 2024 | 2021 | 2021 |
| MSRV | 1.88.0 | 1.71 | 1.71 |
| Owners | 1 | 2 (team) | 3 (team) |
Links
Quick Verdict
- •mio leads with a health score of 76/100, but none of the options score above 80.
- •tokio is depended on by 1.1M crates — strongest ecosystem trust.
- •tcp-stream is pre-1.0 — API may change.