aio-libs/aiohttp

Asynchronous HTTP client/server framework for asyncio and Python

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 3rd, 2026
Created on October 1st, 2013
Open Issues & Pull Requests: 221 (+5)
GitHub issues: Enabled
Number of forks: 2,396
Total Stargazers: 16,543 (+0)
Total Subscribers: 215 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.2 hours
Mean response time: 115.3 days
90th percentile: 208.9 days
Tracked items: 560

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 71% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "reproducer: present" is answered fastest, typically in under an hour, while "Hacktoberfest" waits about 3 days. Only 6% of issues opened in the past year have been closed. Three people close 85% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 105
New in 7 days: 1
Closed in 7 days: 5
Avg open age: 1,729 days
Stale 30+ days: 99
Stale 90+ days: 89

Recent activity

Opened in 7 days: 1
Closed in 7 days: 4
Comments in 7 days: 2
Events in 7 days: 5

Top labels

  • bug (301)
  • enhancement (164)
  • needs-info (115)
  • Stale (95)
  • good first issue (25)
  • Hacktoberfest (21)
  • reproducer: missing (18)
  • client (16)

Detailed Description

aiohttp is an asynchronous HTTP client and server framework for Python's asyncio library.

The tool addresses the need to handle HTTP communication without blocking, allowing concurrent requests and responses through async/await syntax. It provides both client-side capabilities for making HTTP requests and server-side functionality for building web applications. The framework includes built-in support for WebSockets, middleware, and pluggable routing, eliminating callback-based patterns in favor of async/await semantics.

Developers should choose aiohttp when building I/O-bound applications that benefit from concurrency, such as services making many simultaneous HTTP requests or web servers handling numerous concurrent connections. It suits projects already using asyncio or those where non-blocking I/O is a core requirement. The README contrasts its approach with the requests library, noting that aiohttp requires more explicit session management and awaiting because it operates asynchronously rather than synchronously.

The project maintains active continuous integration with automated testing and code coverage tracking. Development activity shows consistent engagement with community discussions and multiple communication channels for support and coordination.