Plugin profile · observed daily since 02 Aug 2026
WordPress REST API – Authentication Broker
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 Joe Hoyle 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.
Very early-stage: 10+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
0 downloads a day over the last 7 days, falling 100% 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 | 16 Aug | 17 Aug | 18 Aug | 19 Aug | 20 Aug | 21 Aug | 22 Aug | 23 Aug | 24 Aug | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (10+) · version (0.1.0) · support threads (0) · threads resolved (0)
28 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 3,614 days (9.9 years). The last was 06 Oct 2016.
- Declares compatibility only up to WordPress 4.7.35, while 7.1 is current. The author has not confirmed it runs on the last 24 releases.
- The same account maintains 3 other plugins, and none has been updated in over a year, the most recent on 05 Aug 2024.
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.
- 02 Aug 202628 days 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.
- 30 Mar 20188 years agoDormancy threshold crossed540 days since the last release (2016-10-06). Dormancy is a maintenance observation, not a judgement about the owner.
- 06 Oct 20169.5 years agoVersion 0.1.0 released
- 06 Oct 20169.5 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 Joe Hoyle for all 28 days we have observed it.
- It was last released 9.5 years ago (06 Oct 2016).
- Its author declares it tested up to WordPress 4.7.35; WordPress is now on 7.1.
- WordPress.org reports 10+ 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.
Disables the WP REST API for visitors not logged into WordPress.
Extends the WP REST API using JSON Web Tokens Authentication as an authentication method.
Connect any REST API to WordPress. WPGet API enables easy API integration, allowing you to display API data without any code.
Secure and protect WordPress REST API from unauthorized access using JWT token, Basic Authentication, API Key, OAuth 2, or external token.
Connect applications to your WordPress site without ever giving away your password.
Disable the use of the REST API on your website to site users. Now with User Role support!
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 WordPress REST API – Authentication Broker: a person reads every submission, and corrections get a reply within 5 business days.