Will Earnhardt

Depending on your server setup, there may be tests in the WordPress Site Health tool that are not relevant and will never pass. For example, you may have background updates disabled if your entire site is kept under version control.
This plugin adds a simple settings page to exclude those tests from the Site Health Status page.
Note: This should only be used to disable tests with a legitimate and acceptable reason for failing. It should not be used to hide tests which can be fixed.
<h4>Credits</h4>
Icon from the <a href="https://www.iconfinder.com/icons/4174309/geometric_heart_heartbeat_hearts_love_valentine_icon" rel="nofollow ugc">Geometric Hearts Valentine’s Day icon set</a> by <a href="https://www.iconfinder.com/Abstracto-create" rel="nofollow ugc">Katerine Melina (Abstracto Create)</a> and licensed under <a href="https://creativecommons.org/licenses/by/3.0/" rel="nofollow ugc">CC by 3.0</a>.

Site Health Tool Manager

This plugin enables me to somewhat control the site Health, and having the luxury to not explain certain things to my customers...

Thanks.

Really Good !

If you manage a website for someone who maintains administrator privileges on the site, but would be bothered by failing tests in WordPress 5.2's new Site Health dashboard, this plugin is an excellent tool. 

Note: you should NOT use this plugin to ignore problems on the site like woefully out-of-date PHP or other critical security issues. Instead, you should resolve the root issue. 

But (for example) if your server/host is unable to update to PHP 7.3 (at the time of this review, that's the recommended version) but is running 7.2... it may be useful to remove that "recommendation" from the list of checks temporarily. 

Another plus in the plus-column: this plugin can even remove tests that are added by third-party code.  

Excellent plugin for developers and power users.

Thanks for making this plugin, essential tool so that clients do not get in panic!

Must-have tool for WP 5.2+ and clients... :-)

Easily control which tests appear in the the Site Health Tool

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.

Site Health Tool Manager vs Lockora Security Audit