Jason Cosper

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.
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.
<h3>Usage</h3>
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.
For the Site Health checks, navigate to Tools → Site Health in your WordPress dashboard.
<h3>Git Updater Support</h3>
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.
Supported platforms:
<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>
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.
Note: “Tested up to” is only available for WordPress.org plugins. Git-hosted plugins will only show “Last updated.”
<h3>Site Health Check</h3>
PLU Redux adds two checks to Tools → Site Health:
<ul>
<li>Outdated plugins – Lists any plugins not updated in 2+ years (critical status).</li>
<li>Untested plugins – Lists plugins not tested with a recent WordPress version (recommended status).</li>
</ul>
<h3>WP-CLI Command</h3>
PLU Redux includes a WP-CLI command: <code>wp plu list</code>
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.

PLU Redux

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

Guido Schad

Lockora Security Audit helps site owners and agencies review a WordPress site’s security posture from the admin area.
Current prototype features include:
<ul>
<li>Manual security scans.</li>
<li>Weighted security score out of 100.</li>
<li>WordPress core file integrity checks using official checksums.</li>
<li>WordPress authentication key and salt checks, with an explicit action to generate missing salts.</li>
<li>Must-use plugin directory presence checks.</li>
<li>PHP version status using WordPress.org Serve Happy data.</li>
<li>HTTPS and HTTP security header checks.</li>
<li>WordPress core, plugin, and theme update posture checks.</li>
<li>Administrator account posture checks for default usernames, excess admins, inactive admins, user ID 1 exposure, and an admin username/email inventory.</li>
<li>Optional known vulnerability matching with a configured Wordfence Intelligence API key.</li>
<li>Optional AI client reports on WordPress 7.0+ when the site’s AI Connector is configured.</li>
<li>Reversible hardening toggles for XML-RPC, REST user routes, generator tag output, and basic security headers.</li>
</ul>
<h3>External Services</h3>
Lockora Security Audit may connect to external services only when the administrator runs a scan or generates an AI client report.
WordPress.org APIs: 
* Used for WordPress core checksums, PHP version support status, and WordPress core/plugin/theme update data. 
* Data sent: the site’s WordPress version and locale for core checksums and PHP compatibility; WordPress itself may send installed plugin and theme slugs/versions to WordPress.org when update data is refreshed. 
* WordPress.org terms: https://wordpress.org/about/terms/ 
* WordPress.org privacy policy: https://wordpress.org/about/privacy/
Wordfence Intelligence: 
* Optional. 
* Used only when a Wordfence Intelligence API key is configured and an administrator runs a scan that includes vulnerability matching. 
* Used to retrieve vulnerability data and match it locally against installed WordPress core, plugin, and theme versions. 
* Data sent: the configured Wordfence Intelligence API key is sent in an Authorization header when requesting the vulnerability feed. Installed software details are not sent by this plugin to the Wordfence Intelligence endpoint; matching is performed locally after the feed is retrieved. 
* Wordfence Intelligence terms: https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/ 
* Wordfence privacy policy: https://www.wordfence.com/privacy-policy/
WordPress AI Client / Connectors: 
* Optional. 
* Used only when the administrator clicks Generate Client Report. 
* Data sent: sanitized scan findings, score, counts, and recommendations needed to generate a client-facing report. The plugin is designed not to send passwords, salts, API keys, raw logs, full user lists, or file contents. 
* The configured AI provider is controlled by the site owner’s WordPress Connector settings. 
* Terms and privacy policy: these depend on the AI provider configured by the site owner in WordPress. Site owners should review the selected provider’s terms and privacy policy before enabling AI reports.

Lockora Security Audit

Lockora Security Audit checks WordPress security posture, hardening, core integrity, vulnerabilities, and optional AI reports.

PLU Redux vs Lockora Security Audit