Decision Workspace
helixrouter vs tokio-sticky-channel vs reqsign-file-read-tokio
Side-by-side comparison of Rust crates
52
helixrouter
experimentalv1.0.2
Adaptive async compute routing engine: per-job strategy selection (inline/spawn/pool/batch/drop) driven by live pressure, EMA latency, and online-learned quality estimates.
49
tokio-sticky-channel
experimentalv0.1.3
Sticky channel pattern for Tokio - routes messages to specific receivers based on ID hash for consistent message delivery
72
reqsign-file-read-tokio
growingv3.0.2
Tokio-based file reader implementation for reqsign
Core Metrics
| helixrouter | tokio-sticky-channel | reqsign-file-read-tokio | |
|---|---|---|---|
| Health Score | 52 | 49 | 72 |
| Total Downloads | 53 | 1.5K | 2.4M |
| 30d Downloads | 0 | 0 | 366.9K |
| Dependents | 0 | 0 | 85 |
| Releases | 3 | 4 | 7 |
| Last Updated | 116d ago | 361d ago | 3d ago |
| Age | 3m | 12m | 10m |
Health Breakdown
helixrouter
Maintenance
13
Quality
16
Community
6
Popularity
2
Documentation
15
tokio-sticky-channel
Maintenance
13
Quality
13
Community
6
Popularity
4
Documentation
13
reqsign-file-read-tokio
Maintenance
23
Quality
17
Community
12
Popularity
8
Documentation
12
Technical Details
| helixrouter | tokio-sticky-channel | reqsign-file-read-tokio | |
|---|---|---|---|
| Version | 1.0.2 | 0.1.3 | 3.0.2 |
| Stable (≥1.0) | ✓ Yes | ✗ No | ✓ Yes |
| License | MIT | MIT/Apache-2.0 | Apache-2.0 |
| Dependencies | 15 | 4 | 4 |
| Crate Size | 142KB | 20KB | 11KB |
| Features | 2 | 0 | 0 |
| Yanked % | 0.0% | 0.0% | 0.0% |
| Edition | 2021 | 2024 | 2024 |
| MSRV | 1.81 | — | 1.85.0 |
| Owners | 1 | 1 | 2 |
Links
Quick Verdict
- •reqsign-file-read-tokio leads with a health score of 72/100, but none of the options score above 80.
- •tokio-sticky-channel is pre-1.0 — API may change.