Jason Cosper

<p>PLU Redux displays the “Last Updated” date and “Tested up to” version for all of your installed plugins. If a plugin hasn’t been updated in over two years – or hasn’t been tested with a recent WordPress version – you’ll get a warning emoji next to the relevant field.</p>
<p>Version 3.0 adds full support for plugins managed by <a href="https://git-updater.com/" rel="nofollow ugc">Git Updater</a>. GitHub, GitLab, Bitbucket, Gitea, and Gist are all supported.</p>
<h3>Usage</h3>
<p>Once activated, head over to your Plugins screen. You’ll see “Last Updated” and “Tested up to” info in the metadata row for each plugin. Warning emojis appear when a plugin hasn’t been updated in over two years or its “Tested up to” version is significantly behind your current WordPress version.</p>
<p>For the Site Health checks, navigate to Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Site Health in your WordPress dashboard.</p>
<h3>Git Updater Support</h3>
<p>PLU Redux automatically detects plugins using <a href="https://git-updater.com/" rel="nofollow ugc">Git Updater</a> headers and queries the appropriate hosting API for last updated info.</p>
<p>Supported platforms:</p>
<ul>
<li>GitHub (<code>GitHub Plugin URI</code>) – checks releases first, falls back to last commit</li>
<li>GitLab (<code>GitLab Plugin URI</code>) – uses <code>last_activity_at</code></li>
<li>Bitbucket (<code>Bitbucket Plugin URI</code>) – uses <code>updated_on</code></li>
<li>Gitea (<code>Gitea Plugin URI</code>) – self-hosted; requires a full URL in the header</li>
<li>Gist (<code>Gist Plugin URI</code>) – uses gist <code>updated_at</code></li>
</ul>
<p>PLU Redux also respects the <code>Primary Branch</code> header. When there’s no release, it falls back to the last commit on the specified branch.</p>
<p>Note: “Tested up to” is only available for WordPress.org plugins. Git-hosted plugins will only show “Last updated.”</p>
<h3>Site Health Check</h3>
<p>PLU Redux adds two checks to Tools <span aria-hidden="true" class="wp-exclude-emoji">→</span> Site Health:</p>
<ul>
<li><strong>Outdated plugins</strong> – Lists any plugins not updated in 2+ years (critical status).</li>
<li><strong>Untested plugins</strong> – Lists plugins not tested with a recent WordPress version (recommended status).</li>
</ul>
<h3>WP-CLI Command</h3>
<p>PLU Redux includes a WP-CLI command: <code>wp plu list</code></p>
<p>This outputs a table of your installed plugins with their last updated dates and tested versions. Plugins needing attention are flagged with an arrow (<code><-</code>). A <code>-</code> in the “Tested Up To” column means the plugin isn’t in the WordPress.org directory.</p>


PLU Redux

Displays the "Last Updated" date and "Tested up to" version for your plugins. Supports WordPress.org and Git Updater plugins.

talkingmonkeymedia

<p><strong>Talking Monkey Insights</strong> gives you a site health snapshot in your WordPress admin — and exposes the same data via a secure REST API so you can monitor multiple sites from your own dashboard.</p>
<h4>What you see in WP Admin</h4>
<ul>
<li><strong>Updates</strong> — count + list of plugins needing updates, theme update count, core update status</li>
<li><strong>Security</strong> — threats blocked, login attempts blocked, last scan results (auto-detected from WordFence or Defender)</li>
<li><strong>Backups</strong> — last backup time, backup count, next scheduled backup (auto-detected from UpdraftPlus or Snapshot)</li>
<li><strong>SSL</strong> — days until expiry with color-coded status</li>
<li><strong>REST API</strong> — endpoint URL + your API key + enable/disable toggle</li>
</ul>
<h4>Why the REST API matters</h4>
<p>If you manage multiple WordPress sites — agency, freelance portfolio, internal IT — built-in WP Site Health is shallow and ManageWP/MainWP require connecting to their proprietary dashboards. This plugin gives you a clean, secure REST endpoint at <code>/wp-json/tm/v1/stats</code> that you can hit from your own dashboard, BI tool, Slack bot, or whatever you already use.</p>
<p>The endpoint requires an API key (auto-generated on activation; regeneratable). No other authentication.</p>
<h4>Multi-ecosystem detection</h4>
<p>Most site monitoring plugins lock you into one ecosystem. This one auto-detects whichever security and backup plugin you have installed:</p>
<ul>
<li><strong>Security:</strong> WordFence or Defender</li>
<li><strong>Backups:</strong> UpdraftPlus or Snapshot</li>
</ul>
<p>Don’t have either installed? The corresponding section shows a neutral “no supported plugin detected” state. No upsells, no recommendations to install anything.</p>
<h4>Privacy</h4>
<p>This plugin does not send any data outside of your WordPress site without your explicit configuration. No telemetry. No analytics. No phone-home.</p>
<p>The REST API endpoint is enabled by default but can be disabled in settings. When enabled, access requires an API key. The plugin only responds to authenticated requests; it never proactively contacts external services.</p>
<h4>Built by an agency that uses it</h4>
<p>Talking Monkey hosts WordPress sites for our own clients. We built this plugin to monitor them from our internal dashboard — and made it free + open source so other agencies and site owners can do the same. We need it to be trustworthy because we install it on every site we host.</p>


Talking Monkey Insights

Site health snapshot and REST monitoring API. Auto-detects WordFence/Defender, UpdraftPlus/Snapshot. Built for agencies running multiple sites.

PLU Redux vs Talking Monkey Insights