graph-gophers/graphql-go

GraphQL server with a focus on ease of use

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 14th, 2026
Created on October 18th, 2016
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 497
Total Stargazers: 4,760 (+0)
Total Subscribers: 82 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.2 days
Mean response time: 281.3 days
90th percentile: 487.1 days
Tracked items: 47

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 438 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

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

Top labels

  • bug (2)
  • good first issue (2)
  • help wanted (2)
  • enhancement (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

graphql-go is a GraphQL server library for Go that emphasizes ease of use and full support for the GraphQL specification.

The library solves the problem of building GraphQL servers in Go by providing an idiomatic, minimal API that maps Go structs and interfaces directly to GraphQL schema types. Resolvers are matched to the schema based on method sets, allowing developers to define resolver logic through exported methods or struct fields that correspond to GraphQL fields. The tool handles the mechanics of GraphQL execution including parallel resolver execution, panic recovery, and context propagation.

The project suits teams building GraphQL APIs in Go who want a straightforward mapping between their Go types and GraphQL schema without heavy boilerplate. It works well for applications that need subscription support, observability through OpenTelemetry and OpenTracing integration, and the ability to inspect selected fields to avoid N+1 query problems. The library's approach of using Go's method sets for resolver matching means developers define their business logic in familiar Go patterns rather than learning a specialized resolver framework.

The project maintains active continuous integration with automated testing across its codebase. Development activity shows consistent attention to specification compliance, with the library tracking updates to the GraphQL specification. The maintainers respond to issues and pull requests, indicating ongoing stewardship of the codebase. The project includes example implementations and documentation through its wiki, suggesting a commitment to helping users understand how to apply the library to realistic use cases.