Features

Everything Keep It Peace checks, how it notifies you, and which external services it contacts.

Most security plugins focus on WordPress core and plugins from WordPress.org. Keep It Peace checks the parts they usually miss, on a schedule, and sends you a summary by e-mail.

Custom themes

  • File integrity against a trusted baseline: added, modified and deleted files.
  • A static scan for dangerous code: eval(), shell execution, obfuscated payloads, unescaped request data, SQL without prepare(), AJAX and REST handlers without nonce or capability checks, and more.

Programs outside WordPress

Landing pages, form mailers or legacy applications on the same server. Register their directories and they get the same file checks as your themes.

The public surface of your site

  • SSL certificate expiry and trust, and the TLS version.
  • Security headers and version disclosure.
  • Publicly downloadable files such as .env, .git, wp-config.php backups, SQL dumps and debug.log.
  • Directory listings.

These checks send requests from your server to your own site only, and are limited to the domain of your site.

PHP and the server

  • End of life and security support of your PHP version, missing patch releases and known CVEs.
  • Risky php.ini settings.
  • MySQL/MariaDB support status.
  • WP_DEBUG and wp-config.php permissions.
  • PHP files in the uploads folder.

Dependencies

Known vulnerabilities in composer.lock and package-lock.json found in themes and registered directories.

Findings with a history

Results are stored as findings with a history. New, resolved and ongoing issues are tracked between scans. You can acknowledge or ignore findings; ignored file findings become active again when the file changes.

E-mail notifications

After each scan you get an e-mail summary (HTML and plain text) with the number of issues by severity, new and resolved issues, the PHP status and the days left on your SSL certificate. File paths and code are never included in e-mails; details stay in your dashboard.

Choose when to send: always, only when there are issues, only for new issues, or above a minimum severity. A weekly digest is optional.

Built for shared hosting

  • No shell commands: exec, shell_exec, proc_open and backticks are not used.
  • Works under open_basedir: directories PHP cannot read are reported instead of causing warnings.
  • Scans run in short slices and resume where they stopped, so they never hit max_execution_time.
  • The plugin only reads files. It never changes or deletes them.
  • Can be run from the server cron with WP-CLI. The PHP version used by the web server is recorded and evaluated even when the scan runs on the CLI.
wp keep-it-peace scan --quiet

For developers

Checks, scan targets, notification channels, rules, settings tabs and the JSON export can be extended through documented interfaces, actions and filters.

External services

Keep It Peace contacts the services below to evaluate your PHP and database versions and your dependencies. Your site URL, file contents and personal data are never sent. Each service can be switched off under Settings → External services, and all of them can be disabled at once. When they are disabled, a bundled snapshot of PHP, MySQL and MariaDB support periods is used.

  • endoflife.date: support periods of PHP, MySQL and MariaDB. Sent: the product name (php, mysql or mariadb).
  • php.net: the latest patch release of your PHP series. Sent: the release series (for example 8.2).
  • NVD (National Vulnerability Database, NIST): known vulnerabilities of your PHP version. Sent: the PHP version (for example 8.2.10).
  • OSV.dev (Google): known vulnerabilities of Composer and npm packages. Sent: package names and versions read from composer.lock and package-lock.json.