BlogSafe.org

BlogSafe Scanner is a lightweight file scanner designed to notify you when any files are modified or uploaded to your server.
It’s features include:
<ul>
<li>Creates a checksum of each file on your web server and compares them to official WordPress checksums. *1</li>
<li>Detects new and modified files on your web server.</li>
<li>Optionally ignore files that are changed often.</li>
<li>Optionally checks plugins and themes against the U.S. NIST National Vulnerability Database for known issues. *2</li>
<li>Optionally hecks plugins and themes for last known updates and alerts you when they haven’t been updated in over 12 months. *2</li>
<li>Sends e-mail alert to the server admin when it’s been deactivated.</li>
<li>Works with WP Multi-site (Activate on parent site only).</li>
<li>Sends e-mail alearts when new or modified files are detected (Plus version).</li>
<li>Scheduling of automatic scans (Plus version).</li>
</ul>
Notes regarding 3rd party services: 
1. BlogSafe Scanner directly contacts various WordPress API’s for checksum verification. 
 During this contact the following information may be sent: 
 a. Plugin name and version. 
 b. Theme name and version. 
 c. WordPress version.
<pre><code>The WordPress Privacy Policy can be found here: [WordPress](https://wordpress.org/about/privacy/ "WordPress Privacy")
</code></pre>
<ol>
<li>
BlogSafe.org monitors and mirrors a portion of the NIST National Vulnerability Database for vulnerabilities related to WordPress, plugins and themes. When opting-in, BlogSafe Scanner will poll the BlogSafe.org API for these potential vulnerabilities. At no time will the plugin contact the NIST database directly. BlogSafe.org also maintains a database of known WordPress themes and plugins. This database is generated directly from the WordPress repository and verified via the WordPress API. When opting-in, BlogSafe scanner will poll the BlogSafe.org API for this data. At no time does BlogSafe Scanner directly contact the WordPress SVN. 
 During this opt-in contact the following information may be sent: 
 a. A list of plugins and themes found on your website along with their versions.
The BlogSafe.org privacy policy can be found here: [BlogSafe] (https://blogsafe.org/privacy-policy/ “BlogSafe Privacy”)
</li>
</ol>

BlogSafe Scanner

BlogSafe Scanner is a lightweight file scanner designed to notify you when any files are…

Erik Torsner

[no-op release – work in progress for version 1.0]
Integrity-checker uses a mix of traditional and new techniques to scan your website for potential issues. First and foremost, it verifies that all installed code is identical to it’s original version. By comparing WordPress core, plugins and themes in your installation with the original versions available at wordpress.org, Integrity-checker can quickly determine if there are any changes you need to be aware of. Integrity-checker also lets you compare your local version to the original to help you determine if you’ve been hacked.
Additionally, Integrity-checker scans all installed files for permission issues. Ensuring correct permissions is vital for WordPress security, as with any PHP based web application.
Lastly, Integrity-checker will look through some of the basic WordPress configuration to look for common security problems like user enumeration, directory index weak credentials etc.
<h4>Features</h4>
<ul>
<li>Helps you track down hacked WordPress files in core, plugins and themes </li>
<li>Makes it easy to find issues with file permissions</li>
<li>Detects common configuration problems</li>
</ul>
<h4>3rd party software</h4>
<a href="https://github.com/mtdowling/cron-expression" rel="nofollow ugc">cron-expression</a> copyright Michael Dowling, see <a href="https://raw.githubusercontent.com/mtdowling/cron-expression/v1.1.0/LICENSE" rel="nofollow ugc">license</a>. Cron-expression is slightly adopted to use the Integrity Checker namespace to avoid potential conflicts.
<a href="https://github.com/chrisboulton/php-diff" rel="nofollow ugc">php-diff</a> copyright Chris Boulton under the <a href="https://opensource.org/licenses/BSD-3-Clause" rel="nofollow ugc">BSD license</a>. php-diff is slightly adopted to use the Integrity Checker namespace to avoid potential conflicts.
<a href="https://github.com/silexphp/Pimple/" rel="nofollow ugc">silexphp/Pimple</a> copyright Fabien Potencier, see <a href="https://github.com/silexphp/Pimple/blob/v3.0.2/LICENSE" rel="nofollow ugc">license</a>. Pimple is slightly adopted to use the Integrity Checker namespace to avoid potential conflicts.
<a href="https://datatables.net" rel="nofollow ugc">DataTables</a> 1.10.13 copyright 2008-2016 SpryMedia Ltd. Licensed under the MIT license, see <a href="https://datatables.net/license" rel="nofollow ugc">datatables.net/license</a>
<a href="https://github.com/arnapou/jqcron" rel="nofollow ugc">jqCron.js</a> Licensed under the MIT license, see <a href="https://github.com/arnapou/jqcron/blob/master/LICENSE" rel="nofollow ugc">license</a>

Integrity Checker

I've modified the review after discussion with the author

This is a very useful tool! The free API limit might be a little low if you want to test the site recurrently but it's still a useful tool.

Promising!

The WordPress Integrity Checker checks your WordPress installation by detecting modified files, permissions issues and other common problems.

BlogSafe Scanner vs Integrity Checker