go-chi/chi

lightweight, idiomatic and composable router for building Go HTTP services

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 22 minutes ago
Added to GitGenius on September 2nd, 2026
Created on October 15th, 2015
Open Issues & Pull Requests: 88 (+0)
GitHub issues: Enabled
Number of forks: 1,158
Total Stargazers: 22,787 (+0)
Total Subscribers: 204 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 77.6 days
90th percentile: 274.4 days
Tracked items: 86

How this project is maintained

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

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 30
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,076 days
Stale 30+ days: 26
Stale 90+ days: 23

Recent activity

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

Top labels

  • routing (4)
  • help wanted (3)
  • v6 (3)
  • context pool (1)
  • review (1)
  • url-params (1)

Most active issues this week

Detailed Description

chi is a lightweight, idiomatic and composable router for building Go HTTP services.

chi addresses the need for a minimal HTTP router that integrates seamlessly with Go's standard library patterns. Rather than imposing a heavy framework, it builds on top of Go's net/http package, allowing developers to write handlers that are compatible with the standard library while gaining routing capabilities. The router supports middleware composition, context-based request handling, and RESTful route patterns, enabling clean separation of concerns in HTTP service code.

Developers should choose chi when building microservices or APIs where simplicity and standards compliance matter more than an all-in-one framework. It suits projects that value idiomatic Go code and want to avoid vendor lock-in to a larger framework ecosystem. The tool works well for teams already comfortable with Go's net/http patterns and seeking to add routing without significant architectural changes.

The project maintains steady, focused development with regular updates addressing bug fixes and minor enhancements. Contributions are accepted and reviewed, indicating an active maintenance posture. The codebase remains lean and purposeful, avoiding feature creep that would compromise the lightweight philosophy stated in its core description.