graphql/graphiql

GraphiQL & the GraphQL LSP Reference Ecosystem for building browser & IDE tools.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 2 minutes ago
Added to GitGenius on September 3rd, 2026
Created on August 11th, 2015
Open Issues & Pull Requests: 390 (+0)
GitHub issues: Enabled
Number of forks: 1,853
Total Stargazers: 16,904 (+0)
Total Subscribers: 236 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.4 days
Mean response time: 110.5 days
90th percentile: 234.9 days
Tracked items: 197

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 98% 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 89% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 90
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 768 days
Stale 30+ days: 86
Stale 90+ days: 82

Recent activity

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

Top labels

  • graphiql (129)
  • bug (119)
  • enhancement (44)
  • lsp-server (30)
  • @graphiql/react (5)
  • graphql-language-service (5)
  • monaco-graphql (5)
  • vscode-graphql (5)

Most active issues this week

Detailed Description

GraphiQL is a monorepo providing reference implementations and tools for building GraphQL IDEs in browsers and code editors.

The monorepo addresses the need for standardized, specification-compliant tooling to support GraphQL development across different environments. It provides a language service that powers IDE features like autocompletion, linting, and documentation lookup. The core GraphiQL package is a React-based in-browser IDE that connects to GraphQL servers, while additional packages extend this functionality to different editors: CodeMirror 5 and 6 modes for syntax highlighting and intelligent editing, and a Monaco editor mode for VS Code-like environments. The language service itself can be used standalone as an LSP server or CLI tool, allowing any IDE to integrate GraphQL support.

Developers should adopt this if they need to embed a GraphQL IDE in a web application, add GraphQL editing capabilities to an existing editor, or build custom IDE tooling. The monorepo structure makes it suitable for projects ranging from simple GraphiQL instances for a single server to complex IDE extensions and plugins. The project is the official reference implementation under the GraphQL Foundation, meaning it tracks the GraphQL specification closely and provides the canonical approach to language features like autocompletion and validation.

The project maintains active development across multiple packages with regular updates to support new GraphQL features and editor integrations. Maintenance spans both the core GraphiQL IDE and the underlying language service that powers editor integrations, indicating sustained investment in the entire ecosystem. The monorepo structure allows independent versioning and updates of different components, enabling teams to adopt pieces of the ecosystem incrementally rather than as a single package.