hyperium/hyper

An HTTP library for Rust

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 55 minutes ago
Added to GitGenius on September 3rd, 2026
Created on August 30th, 2014
Open Issues & Pull Requests: 245 (+0)
GitHub issues: Enabled
Number of forks: 1,798
Total Stargazers: 16,310 (+0)
Total Subscribers: 177 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.8 hours
Mean response time: 48.7 days
90th percentile: 101.3 days
Tracked items: 218

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 88% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "A-http2" is answered fastest, typically in about an hour, while "E-medium" waits about 10 days. Only 5% of issues opened in the past year have been closed. Three people close 84% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 57
New in 7 days: 0
Closed in 7 days: 5
Avg open age: 1,035 days
Stale 30+ days: 21
Stale 90+ days: 21

Recent activity

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

Top labels

  • C-bug (86)
  • C-feature (72)
  • E-easy (34)
  • K-hyper-util (33)
  • A-client (26)
  • B-rfc (16)
  • A-server (15)
  • A-http1 (14)

Detailed Description

hyper is an HTTP library for Rust that provides low-level building blocks for constructing HTTP clients and servers.

The library addresses the need for a performant, correct, and production-ready HTTP implementation in Rust by offering asynchronous APIs that support both HTTP/1 and HTTP/2 protocols. Its design prioritizes efficiency and correctness, with extensive testing and a track record of use in production systems.

Developers should choose hyper if they are building libraries or applications that need direct control over HTTP behavior. It is well-suited for projects requiring high performance and protocol compliance. The README positions hyper as a foundation layer: for those seeking a convenient HTTP client, reqwest is recommended as a higher-level alternative; for HTTP server use cases, axum and warp are suggested as more ergonomic options built on top of hyper itself.

Almost all open issues are raised by outside users rather than the core team, reflecting a substantial base of adopters reporting real-world use. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker is dominated by bug reports, feature requests, and easy-to-tackle tasks.