Plugin profile · observed daily since 02 Aug 2026
Purge Varnish Cache
Active installs1,000+ rounded
Current authorDsingh
Owner changesNone while we have been watching
Last release3 months ago 02 Jun 2026
Support— no recent threads
Releases on record15
Rating5.0 /5 · 10
Added to directory01 Nov 2016
Requires WP4.0
Requires PHPfalse
Version lag0.1 behind
Tested up toWP 7.0.4 WordPress is now on 7.1
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 Dsingh 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 |
|---|---|---|---|
| devavi | 15 | 08 Dec 2016 | 02 Jun 2026 |
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.
Moderately adopted: 1,000+ active installs. A real user base, well short of the ecosystem’s larger plugins.
13 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.
08 Aug 2026peak 78/day05 Sep 2026
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 | 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 | 05 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 11 | 11 | 11 | 11 | 0 | 22 | 0 | 11 | 23 | 11 | 22 | 11 | 11 |
Unchanged throughout: ratings total (10) · active installs (1,000+) · version (1.1.5) · support threads (0) · threads resolved (0)
35 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory9.5 years ago 01 Nov 2016
Requires WP4.0
Requires PHPfalse
Version lag0.1 behind
Is anyone still maintaining this?
- Last released 02 Jun 2026, 95 days ago.
- Declares compatibility only up to WordPress 7.0.4, while 7.1 is current. The author has not confirmed it runs on the last 1 release.
- Dsingh 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.
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.
- 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.
- 02 Jun 20263 months agoVersion 1.1.5 released
- 04 Feb 20242.5 years agoVersion 1.1.4 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.2 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.3 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.4 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.5 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.6 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.7 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.8 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.0.9 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.1.0 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.1.1 releasedfrom the release logCommitted by devavi.
- 01 Nov 20223.5 years agoVersion 1.1.2 releasedfrom the release logCommitted by devavi.
- 08 Dec 20169.5 years ago2 earlier releasesfrom the release logBetween 08 Dec 2016 and 01 Nov 2022. Listed individually in the public release log rather than here.
- 01 Nov 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 Dsingh for all 35 days we have observed it.
- It was last released 3 months ago (02 Jun 2026).
- Its author declares it tested up to WordPress 7.0.4; WordPress is now on 7.1.
- WordPress.org reports 1,000+ active installs.
- It carries 10 ratings, averaging 5.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.
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.
Server-Side Cache AutoPurge
Purge server-side cache automatically after making website changes. Optimized for servers managed by SureSupport.
10,000+ installs4.2★ (5)updated 15 Jun 2026
10× the installs
Compare side by side Proxy Cache Purge
Automatically empty proxy cached content when your site is modified.
50,000+ installs4.4★ (26)updated 02 Sep 2026
50× the installs
Compare side by side CLP Varnish Cache
CLP Varnish Cache lets you configure the cache lifetime, paths, and parameters to exclude from caching. You can purge single urls or cache entries by …
10,000+ installs5.0★ (7)updated 17 Mar 2026
10× the installs
Compare side by side Nginx Cache
Purge the Nginx cache (FastCGI, Proxy, uWSGI) automatically when content changes or manually within WordPress.
10,000+ installs4.6★ (23)updated 04 May 2026
10× the installs
Compare side by side Hestia Nginx Cache
Purged the Nginx cache automatically after making website changes. Uses the new HestiaCP API, released in 1.6.0.
1,000+ installs5.0★ (9)updated 28 Aug 2026
Compare side by side Clear Cache for Me
Purges cache on WPEngine, W3TC, WP Super Cache, WP Fastest Cache when widgets, menus, settings update. Forces browsers to reload CSS and JS files.
40,000+ installs4.8★ (29)updated 18 Jun 2026
40× the installs
Compare side by side 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 Purge Varnish Cache: a person reads every submission, and corrections get a reply within 5 business days.