wp-graphql/wp-graphql

:rocket: GraphQL API for WordPress

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on September 18th, 2026
Created on October 31st, 2016
Open Issues & Pull Requests: 150 (+0)
GitHub issues: Enabled
Number of forks: 476
Total Stargazers: 3,791 (+0)
Total Subscribers: 58 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.3 days
Mean response time: 126.3 days
90th percentile: 500.8 days
Tracked items: 264

Maintainer activity

4 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. Only 17% of open issues come from outside the core team — the tracker reads mainly as internal planning. Work labelled "impact: high" is answered fastest, typically in about 11 hours, while "effort: low" waits about 10 days. 32% of tracked open issues have had no activity in three months. Only 55% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 110
New in 7 days: 13
Closed in 7 days: 5
Avg open age: 858 days
Stale 30+ days: 80
Stale 90+ days: 54

Recent activity

Opened in 7 days: 13
Closed in 7 days: 5
Comments in 7 days: 1
Events in 7 days: 75

Top labels

  • impact: med (92)
  • type: enhancement (85)
  • type: bug (80)
  • status: actionable (71)
  • needs: discussion (65)
  • effort: low (64)
  • effort: med (63)
  • scope: api (44)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

WPGraphQL is a GraphQL API plugin for WordPress that exposes WordPress data through a standards-based GraphQL schema.

The plugin solves the problem of accessing WordPress data in modern development workflows by providing a complete GraphQL interface to WordPress core features including posts, pages, users, and taxonomies. Rather than relying on REST endpoints, developers query exactly the data they need through a single GraphQL endpoint, reducing over-fetching and simplifying client-side data management. The implementation follows GraphQL and WordPress best practices and is designed to be extensible, allowing plugins to add their own schema definitions on top of the core WordPress schema.

Developers should choose WPGraphQL if they are building modern applications on WordPress and want to leverage GraphQL's query efficiency and developer experience. It suits projects ranging from headless WordPress sites to Gatsby integrations to any application that needs programmatic access to WordPress data. The tool distinguishes itself by maintaining a clear scope: core features cover WordPress's built-in functionality and performance optimizations that benefit all users, while plugin-specific integrations and opinionated workflows are intentionally kept as separate extensions. This separation keeps the core maintainable while enabling a rich ecosystem of add-ons for ACF, Yoast, WooCommerce, and other popular WordPress tools.

The project maintains an active development process with a structured approach to new functionality. The team uses an Experiments framework to validate proposed features and breaking changes in real-world conditions before committing them to core, allowing community feedback to inform decisions about stability and backward compatibility. The codebase is organized as a monorepo containing the WPGraphQL ecosystem of plugins and supporting websites, with clear documentation for both end users installing from standard channels and contributors setting up a development environment.