grpc-ecosystem/grpc-gateway

gRPC to JSON proxy generator following the gRPC HTTP spec

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 minute ago
Added to GitGenius on September 2nd, 2026
Created on April 3rd, 2015
Open Issues & Pull Requests: 149 (-1)
GitHub issues: Enabled
Number of forks: 2,408
Total Stargazers: 19,997 (+0)
Total Subscribers: 274 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.2 hours
Mean response time: 23.0 days
90th percentile: 5.3 days
Tracked items: 168

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 86% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "bug" is answered fastest, typically in about 7 hours, while "OpenAPI v3" waits about 5 days. Only 6% of issues opened in the past year have been closed. Three people close 88% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 48
New in 7 days: 2
Closed in 7 days: 2
Avg open age: 810 days
Stale 30+ days: 41
Stale 90+ days: 37

Recent activity

Opened in 7 days: 2
Closed in 7 days: 2
Comments in 7 days: 5
Events in 7 days: 10

Top labels

  • help wanted (39)
  • bug (29)
  • openapi (28)
  • good first issue (19)
  • OpenAPI v3 (14)
  • enhancement (11)
  • question (6)
  • documentation (3)

Detailed Description

gRPC-Gateway is a protoc plugin that generates a reverse-proxy server translating RESTful HTTP APIs into gRPC calls.

The tool solves the problem of serving both gRPC and RESTful JSON interfaces from a single service definition. It reads protobuf service definitions annotated with google.api.http directives and generates a reverse-proxy server that converts incoming HTTP requests into gRPC calls, then translates the responses back to JSON. This approach lets you maintain a single backend service while exposing it through both gRPC and REST protocols without duplicating business logic.

Teams should adopt this tool when they need to support REST clients alongside gRPC clients, whether for backward compatibility with existing REST consumers, supporting languages with limited gRPC tooling, or meeting organizational standards around RESTful APIs. It suits projects already using protocol buffers and gRPC where adding HTTP+JSON support is a requirement. The tool requires only minimal configuration—adding HTTP annotations to your existing protobuf definitions—making it a low-friction addition to established gRPC services.

The project maintains active continuous integration with automated builds. Development activity shows consistent engagement with the codebase through regular updates and maintenance of the core proxy generation and routing logic.