rust-lang/futures-rs

Zero-cost asynchronous programming in Rust

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 11th, 2026
Created on March 30th, 2016
Open Issues & Pull Requests: 275 (+0)
GitHub issues: Enabled
Number of forks: 707
Total Stargazers: 5,919 (+0)
Total Subscribers: 94 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.8 days
Mean response time: 183.3 days
90th percentile: 633.4 days
Tracked items: 70

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 87% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 6% of issues opened in the past year have been closed. Three people close 94% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 61
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 827 days
Stale 30+ days: 58
Stale 90+ days: 54

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • C-feature-request (13)
  • A-stream (12)
  • bug (7)
  • A-future (6)
  • A-channel (5)
  • C-question (4)
  • docs (4)
  • A-io (3)

Most active issues this week

Detailed Description

Futures-rs is a library providing the foundations for asynchronous programming in Rust.

The library addresses the need for ergonomic and efficient async control flow by offering core trait definitions like Stream alongside utilities such as join!, select!, and combinator methods. These primitives enable developers to compose asynchronous operations expressively without runtime overhead. The project works in both standard and no_std environments, though the API surface is reduced when the standard library is unavailable.

Futures-rs suits projects that need foundational async abstractions rather than a complete runtime. It is particularly valuable for library authors building async ecosystems and for applications requiring fine-grained control over asynchronous composition. The tool provides the building blocks that higher-level async frameworks depend on, making it essential infrastructure for Rust's async ecosystem rather than a batteries-included solution for end-user applications.

The project receives most of its issue reports from outside users rather than the core team, reflecting a substantial base of real-world adopters. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker centers on feature requests, stream-related improvements, and bug fixes.