Disable XML-RPC – Dashboard Control

Ownership

Held by aph5 throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.

Full observed history, including every field transition

Committing accounts

Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.

This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.

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: 20+ active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.

3 downloads a day over the last 7 days, steady against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.

Install band rose to 20+ on 22 Oct 2026, from 10+. Both figures are rounded to one significant digit, so the size of the change is not knowable from them.

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.

Unchanged throughout: ratings total (0) · version (1.0.4) · support threads (0) · threads resolved (0)

91 days of observation, most recent 14 shown.

Maintenance

When it was last released, and how far its declared compatibility has drifted from current WordPress.

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.

Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.

1. 24 Sep 20261 month ago
   Install band moved to 10+Bands are rounded to one significant digit, so the size of the change is not knowable.
2. 10 Sep 20262 months ago
   Version 1.0.4 released
3. 02 Aug 20263 months ago
   Install band moved to fewer than 10Bands are rounded to one significant digit, so the size of the change is not knowable.
4. 02 Aug 20263 months ago
   First observed by PluginsPediaDaily 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.
5. 01 Jul 20264 months ago
   Version 1.0.3 released
6. 01 Jul 20264 months ago
   Version 1.0.2 releasedfrom the release logCommitted by aph5.
7. 24 Jan 20269 months ago
   Version 1.0.0 releasedfrom the release logCommitted by aph5.
8. 24 Jan 20269 months ago
   Version 1.0.1 releasedfrom the release logCommitted by aph5.
9. 24 Jan 20269 months ago
   Added 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.

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

Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.

Limit Login Attempts Security – Login Security, 2FA, Firewall, Brute Force Prevention

WordPress login security with brute force protection, Two-factor authentication (2FA/MFA), firewall, IP/country blocking, and login monitoring

1,000,000+ installs4.8★ (1,488)updated 23 Sep 2026

security

MainWP Child – Securely Connects to the MainWP Dashboard to Manage Multiple Sites

MainWP Child establishes a secure link between your WordPress sites and your self-hosted MainWP Dashboard, simplifying site management.

700,000+ installs5.0★ (71)updated 29 Oct 2026

security

Anti Browser DDoS Protection

Protects WordPress from DDoS with rate limiting, bot detection, blocking, Cloudflare support, logs, charts, and bot list export/import.

30+ installs5.0★ (1)updated 23 Jul 2026

rate limitingsecurity

Automattic For Agencies Client

Securely connect your clients’ sites to the Automattic for Agencies Sites Dashboard. Manage your sites from one place and see what needs attention.

20,000+ installs5.0★ (2)updated 14 Oct 2026

dashboard

Kadence Central – Site Management, Backups, Security, and Reporting

Manage multiple WordPress sites from one dashboard.

30,000+ installs4.2★ (5)updated 19 Aug 2026

security

MainWP Dashboard: Self-hosted WordPress Management for Agencies

Run updates, backups, security and reporting across all client sites from your own server. Keep data private and prove your value with branded reports …

20,000+ installs4.9★ (2,354)updated 29 Oct 2026

security

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 Disable XML-RPC – Dashboard Control: a person reads every submission, and corrections get a reply within 5 business days.