tokio
Cargov1.53.1An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.
Not recommended for new projects
No — tokio should not be adopted for new projects. No license declared — you have no explicit right to use this code.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 51 days ago. 38 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- FLicense: grade F, Failing.
No license declared — you have no explicit right to use this code.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding tokio to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Rust edition
- No constraint declared
tokio vs the alternatives
Packages solving a similar problem in the cargo ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| tokiothis page | 0 | 0 | — | 1 month ago |
| async-trait | 0 | 0 | — | 1 day ago |
| tracing | 0 | 0 | — | 1 day ago |
| actix-web | 0 | 0 | — | 1 day ago |
Release history
36 releases in the last two years, typically about 2 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.53.1latest | 1 month ago | — | MIT |
| 1.53.0 | 1 month ago | — | MIT |
| 1.52.4 | 1 month ago | — | MIT |
| 1.51.4 | 1 month ago | — | MIT |
| 1.52.3 | 4 months ago | — | MIT |
| 1.51.3 | 4 months ago | — | MIT |
| 1.47.5 | 4 months ago | — | MIT |
| 1.52.2 | 4 months ago | — | MIT |
| 1.51.2 | 4 months ago | — | MIT |
| 1.52.1 | 4 months ago | — | MIT |
| 1.52.0 | 4 months ago | — | MIT |
| 1.51.1 | 5 months ago | — | MIT |
| 1.51.0 | 5 months ago | — | MIT |
| 1.47.4 | 5 months ago | — | MIT |
| 1.50.0 | 6 months ago | — | MIT |
Overview
tokio is an Cargo package that an event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications. The latest version is 1.53.1.
Who should use it
Teams working in the Cargo ecosystem who need an event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your Cargo stack.
Pros
- Zero runtime dependencies — minimal footprint.
Cons
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Frequently asked questions
Should I use tokio?
No — tokio should not be adopted for new projects. No license declared — you have no explicit right to use this code.
How do I install tokio?
Run `cargo add tokio` to add tokio to your Cargo project.
What license is tokio released under?
No license was detected in tokio's metadata; review the repository before use.
Is tokio still maintained?
The most recent release of tokio (v1.53.1) was published 1 month ago.