connectrpc/connect-go

The Go implementation of Connect: Protobuf RPC that works.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 17th, 2026
Created on August 2nd, 2021
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 157
Total Stargazers: 4,082 (+0)
Total Subscribers: 29 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.3 hours
Mean response time: 35.7 days
90th percentile: 39.2 days
Tracked items: 56

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 687 days
Stale 30+ days: 13
Stale 90+ days: 6

Recent activity

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

Top labels

  • enhancement (27)
  • bug (16)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Connect-go is a Protobuf RPC framework for Go that provides an alternative to gRPC for building service-to-service communication.

Connect addresses the complexity and operational challenges of traditional gRPC by offering a simpler, more pragmatic approach to Protobuf-based RPC. It works by generating idiomatic Go code from Protobuf definitions and handling request-response serialization with support for multiple protocols. The framework eliminates much of gRPC's boilerplate while maintaining compatibility with Protobuf as the interface definition language, allowing developers to define services once and use them across different transport mechanisms.

Developers should choose Connect-go if they want a lighter-weight alternative to gRPC that reduces operational complexity without sacrificing type safety or code generation benefits. It suits projects where teams prefer simpler HTTP semantics over gRPC's HTTP/2 requirements, or where interoperability with non-gRPC clients matters. The project explicitly positions itself as an alternative to gRPC, offering a more straightforward developer experience while still leveraging Protobuf's strengths.

The project shows consistent, focused development activity with regular maintenance and incremental improvements. The codebase demonstrates attention to API stability and backward compatibility through careful versioning practices. Development follows a structured approach to feature additions and bug fixes, with clear prioritization of reliability over rapid feature expansion. The maintainers actively engage with the community through issue responses and documentation updates, indicating sustained commitment to the project's evolution and user support.