Plugin profile · observed daily since 02 Aug 2026
Disable Autocomplete
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 Andrew Gunn 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.
| Account | Releases | First | Last |
|---|---|---|---|
| amg26 | 1 | 22 Jul 2016 | 22 Jul 2016 |
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.
Small but established: 100+ active installs. Enough sites to show it works in the wild, too few for adoption to say much on its own.
2 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.
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 | 15 Aug | 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 11 | 0 |
Unchanged throughout: ratings total (4) · active installs (100+) · version (1.0) · support threads (0) · threads resolved (0)
27 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,691 days (10.1 years). The last was 20 Jul 2016.
- Declares compatibility only up to WordPress 4.5.33, while 7.1 is current. The author has not confirmed it runs on the last 26 releases.
- The same account maintains 10 other plugins, and none has been updated in over a year, the most recent on 10 Apr 2018.
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 202627 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.
- 11 Jan 20188.5 years agoDormancy threshold crossed540 days since the last release (2016-07-20). Dormancy is a maintenance observation, not a judgement about the owner.
- 22 Jul 201610 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
- 20 Jul 201610 years agoVersion 1.0 released
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 Andrew Gunn for all 27 days we have observed it.
- It was last released 10 years ago (20 Jul 2016).
- Its author declares it tested up to WordPress 4.5.33; WordPress is now on 7.1.
- WordPress.org reports 100+ active installs.
- It carries 4 ratings, averaging 3.0 out of 5.
What we don’t know yet
- 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.
Disable the browser's ability to autofill forms and input fields. Ideal for forms with sensitive information and provides extra level of form sub …
Disable the browser's ability to autofill forms and input fields on selected Gravity Forms. Ideal for forms with sensitive information and provid …
Autofill form fields from PDF and Word documents using the Zaptic service. Requires Ninja Forms.
Autofill form fields from PDF and Word documents using the Zaptic service. Requires WPForms.
Add shortcode for fields autofill of Contact Form 7 plugin by URL get variable, by Id or by value, or add new value(s).
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 Autocomplete: a person reads every submission, and corrections get a reply within 5 business days.