Patch Gap – Update Coverage & Expired License Auditor
Your updates page says everything is fine. It might be lying to you. WordPress.org plugins get a safety net: WordPress checks them for updates automatically, and security plugins warn you when one is abandoned. Premium plugins get nothing. When a premium plugin’s licence expires, its key goes missin
Your updates page says everything is fine. It might be lying to you.
WordPress.org plugins get a safety net: WordPress checks them for updates automatically, and security plugins warn you when one is abandoned.
Premium plugins get nothing.
When a premium plugin’s licence expires, its key goes missing, it was hand-uploaded from a zip, or its vendor quietly disappears, the plugin’s updater stops answering. And here is the dangerous part: a plugin that cannot be updated does not show a warning. It shows nothing at all – which looks identical to a plugin that is perfectly up to date.
So the plugin sits there, at the version it was when the licence lapsed, and never receives another security patch. Your dashboard stays green. Your fleet-management tool stays green. Nobody tells you.
Patch Gap closes that blind spot. It forces every update source on the site to answer, then reports who – if anyone – is actually patching each plugin and theme .
What it tells you
Every plugin and theme is sorted into one of these:
- Covered – WordPress.org. WordPress checks it for you.
- Covered – vendor updater active. A licensed premium plugin whose updater is registered and responding. Working correctly.
- GAP – updater present but silent. The component ships licence/updater code (Freemius, EDD Software Licensing, Plugin Update Checker, WooCommerce API Manager…) but registered no update source. Its licence has almost certainly expired, its key is missing, or it was installed outside the vendor’s channel. It will never be patched again.
- GAP – declares an update source that never answers. It advertises an Update URI, but nothing responds. The vendor may be gone.
- Abandoned upstream. Still on WordPress.org, but not updated in years – or closed entirely.
- No updater (bespoke). Custom or in-house code with no update source and no licence – expected, so Patch Gap lists it without treating it as a problem.
That last one matters: a naive “is it in the update list?” check would scream about every custom plugin an agency has ever written. Patch Gap looks at four independent signals before it calls something a gap, so it flags the components that are genuinely unpatchable – not the ones that are simply bespoke.