Plugin profile · observed daily since 02 Aug 2026
WPGraphQL Blocks
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Tom Phillips throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Small but established: 300+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
5 downloads a day over the last 7 days, falling 68% against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 11 | 0 | 11 | 29 | 11 | 25 | 0 | 0 | 0 | 12 | 0 | 22 | 0 |
Unchanged throughout: ratings total (0) · active installs (300+) · version (2.2.0) · support threads (0) · threads resolved (0)
34 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- No release in 555 days (1.5 years). The last was 26 Feb 2025.
- Declares compatibility only up to WordPress 6.7.7, while 7.1 is current. The author has not confirmed it runs on the last 4 releases.
- Tom Phillips publishes no other plugin in the directory, so there is no wider activity to compare against.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
- 20 Aug 202615 days agoDormancy threshold crossed540 days since the last release (2025-02-26). Dormancy is a maintenance observation, not a judgement about the owner.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 26 Feb 202518 months agoVersion 2.2.0 released
- 13 May 20233 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Tom Phillips for all 34 days we have observed it.
- It was last released 18 months ago (26 Feb 2025).
- Its author declares it tested up to WordPress 6.7.7; WordPress is now on 7.1.
- WordPress.org reports 300+ active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
What can’t be known
- Whether the quiet is neglect or a finished plugin. That is the author’s intent, which no dataset records, and a stable plugin can need no changes for years.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
This plugin has not been updated in a long time. These carry the same tags and describe themselves in the same terms, so they are a starting point for a replacement, not a recommendation. Check them yourself.
WPGraphQL adds a flexible and powerful GraphQL API to WordPress, enabling efficient querying and interaction with your site's data.
Ship your headless WooCommerce storefront faster. CoCart is the REST API built for Next.js, React, Vue, and any modern frontend — developer-first.
Expose redirects set up in Redirection plugin to GraphQL API.
A REST API for headless Next.js sites: a page's post, SEO, and site data in one request, plus cookie login for authenticated front ends.
Exposes Gutenberg block inline styles and the global stylesheet over the REST API for headless frontends like Next.js.
Uses site_url() instead of home_url() to build the API URL. Useful for having WordPress as a Headless CMS.
Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about WPGraphQL Blocks: a person reads every submission, and corrections get a reply within 5 business days.