Decision Workspace
tcp-stream vs mio vs tokio
Side-by-side comparison of Rust crates
68
tcp-stream
growingv0.34.3
std::net::TcpStream on steroids
74
mio
stablev1.2.0
Lightweight non-blocking I/O.
74
tokio
stablev1.50.0
An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Core Metrics
| tcp-stream | mio | tokio | |
|---|---|---|---|
| Health Score | 68 | 74 | 74 |
| Total Downloads | 8.3M | 621.8M | 584.2M |
| 30d Downloads | 899.1K | 46.8M | 43.0M |
| Dependents | 211 | 6.5K | 599.9K |
| Releases | 101 | 77 | 181 |
| Last Updated | 3d ago | today | 24d ago |
| Age | 6y 10m | 11y 4m | 9y 9m |
Health Breakdown
tcp-stream
Maintenance
19
Quality
14
Community
12
Popularity
8
Documentation
15
mio
Maintenance
20
Quality
15
Community
19
Popularity
8
Documentation
12
tokio
Maintenance
17
Quality
17
Community
20
Popularity
8
Documentation
12
Technical Details
| tcp-stream | mio | tokio | |
|---|---|---|---|
| Version | 0.34.3 | 1.2.0 | 1.50.0 |
| Stable (≥1.0) | ✗ No | ✓ Yes | ✓ Yes |
| License | BSD-2-Clause | MIT | MIT |
| Dependencies | 10 | 6 | 34 |
| Crate Size | 28KB | 106KB | 878KB |
| Features | 16 | 4 | 16 |
| Yanked % | 9.9% | 10.4% | 2.8% |
| 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 74/100, but none of the options score above 80.
- •tokio is depended on by 599.9K crates — strongest ecosystem trust.
- •tcp-stream is pre-1.0 — API may change.