Tokio
@tokio-rs • Rust's asynchronous runtime.. Use this route to separate flagship concentration from portfolio breadth before you treat a publisher as broadly strong.
Portfolio concentration
59%
Top three share
Shows whether the organization is driven by one breakout repo or several visible projects.
Breadth
30 repos
Visible snapshot
11 repositories updated in the last 90 days.
Leading language
Rust
Portfolio mix
Rust (25), Unknown (4), TypeScript (1)
Average size
2.2K
Stars per repository
Useful for distinguishing one flagship-heavy publisher from a repeatable portfolio.
Updated: 2026-06-19(41d ago)GitHub API fallback30 repositories
59%
of the visible star count comes from this organization's top three repositories.
2.2K
stars per repository in this same snapshot.
Rust
is the most common language here, with 11 repositories updated in the last 90 days.
Why this rank
This organization stands out because its public portfolio is relatively balanced across 30 repositories.
Balanced portfolio across 30 reposTop 3 share 59%
Organization pages work best when you separate portfolio breadth from flagship concentration. In Tokio's case, the visible top three repositories account for about 59% of total stars in this snapshot, which helps explain whether the organization is known for one breakout project or for a broader repeatable portfolio.
The dominant language mix here is Rust (25), Unknown (4), TypeScript (1). That makes this page useful not just for popularity checks, but also for seeing what technical shape an organization's public ecosystem actually has.
Top Repositories
| # | Repository | Language | Stars |
|---|---|---|---|
| 1 | tokio-rs/axum HTTP routing and request-handling library for Rust that focuses on ergonomics and modularity | Rust | 26.7K |
| 2 | tokio-rs/tracing Application level tracing for Rust. | Rust | 6.8K |
| 3 | tokio-rs/mini-redis Incomplete Redis client and server implementation using Tokio - for learning purposes only | Rust | 4.7K |
| 4 | tokio-rs/prost PROST! a Protocol Buffers implementation for the Rust Language | Rust | 4.7K |
| 5 | tokio-rs/console a debugger for async rust! | Rust | 4.6K |
| 6 | tokio-rs/topcoat A batteries-included framework for building web apps | Rust | 3.9K |
| 7 | tokio-rs/toasty An async ORM for Rust | Rust | 3K |
| 8 | tokio-rs/loom Concurrency permutation testing tool for Rust. | Rust | 2.8K |
| 9 | tokio-rs/io-uring The `io_uring` library for Rust | Rust | 1.7K |
| 10 | tokio-rs/tokio-uring An io_uring backed runtime for Rust | Rust | 1.5K |
| 11 | tokio-rs/turmoil Add hardship to your tests | Rust | 1.2K |
| 12 | tokio-rs/async-stream Asynchronous streams for Rust using async & await notation | Rust | 764 |
| 13 | tokio-rs/rdbc Rust DataBase Connectivity (RDBC) :: Common Rust API for database drivers | Rust | 584 |
| 14 | tokio-rs/tokio-metrics Utilities for collecting metrics from a Tokio application | Rust | 423 |
| 15 | tokio-rs/tracing-opentelemetry | Rust | 404 |
| 16 | tokio-rs/tls A collection of Tokio based TLS libraries. | Rust | 261 |
| 17 | tokio-rs/valuable | Rust | 253 |
| 18 | tokio-rs/async-backtrace | Rust | 209 |
| 19 | tokio-rs/tokio-io Core I/O primitives for asynchronous I/O in Rust. | Rust | 125 |
| 20 | tokio-rs/simulation Framework for simulating distributed applications | Rust | 106 |
| 21 | tokio-rs/tokio-compat Streamline updating a Tokio 0.1 application to Tokio 0.2. | Rust | 52 |
| 22 | tokio-rs/doc-push Tokio doc blitz effort - A concerted effort to improve Tokio's documentation. | 52 | |
| 23 | tokio-rs/book | 48 | |
| 24 | tokio-rs/async Utilities building on top of Rust's async primitives. | Rust | 24 |
| 25 | tokio-rs/tokio-rfcs | 22 | |
| 26 | tokio-rs/tokio-taskdump Utilities for taking taskdumps of Tokio tasks | Rust | 14 |
| 27 | tokio-rs/console-gsoc Google Summer of Code tokio-console prototype | Rust | 14 |
| 28 | tokio-rs/gsoc Organize the Google Summer of Code projects. | 6 | |
| 29 | tokio-rs/cargo-tokio A cargo subcommand to help building the Tokio project. | Rust | 5 |
| 30 | tokio-rs/website-next Next iteration of the Tokio website. | TypeScript | 0 |
Next step after the organization read
Open a flagship repository, compare a couple of portfolio leaders, or return to the organization map when you want a broader concentration read.
Learn and methodology
Keep trust-building context reachable, but behind the first data read instead of ahead of it.
How to read this organization snapshot
Total stars are useful as a discovery signal, but they do not tell you whether a team maintains every repository equally. Pair this page with release cadence, maintainer activity, and the flagship concentration shown above before making adoption decisions.
For broader background on GitStar's ranking logic and editorial guidance, see Methodology & Editorial Standards.