vincentbean

Vigilant Healthchecks provides a REST healthcheck endpoint at <code>/wp-json/vigilant/v1/health</code> with an admin interface to conrol which checks are executed. 
This plugin is designed to integrate with <a href="https://govigilant.io" rel="nofollow ugc">Vigilant</a>, an all-in-one web monitoring tool which can be self-hosted.
<h4>Key Features</h4>
<ul>
<li>Protected REST endpoint with configurable token.</li>
<li>Built-in checks for database connectivity, core versions, plugin updates, cron freshness, Redis, and WordPress Site Health issues.</li>
<li>Metrics catalogue for memory, disk, CPU load, and database size with sensible caching defaults.</li>
<li>Extensible registry and hooks (<code>vigilant_healthchecks_prepare</code>, <code>vigilant_healthchecks_cron_threshold</code>, <code>vigilant_healthchecks_database_size_cache_ttl</code>) so you can add custom checks and metrics.</li>
<li>Scheduler heartbeat (<code>vigilant_healthchecks_cron_monitor</code>) that validates WP-Cron is actually running and reports stale schedules.</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Configure the bearer token under Settings → Vigilant Healthchecks; every REST request must include <code>Authorization: Bearer <token></code>.</li>
<li>Toggle the checks and metrics you want to expose; disabled items are never instantiated so they have zero runtime impact.</li>
<li>Call the endpoint yourself or configure your website in Vigilant.</li>
</ol>

Vigilant Healthchecks

A WordPress plugin that provides healthchecks to your WordPress site that integrate seamlessly with Vigilant (https://govigilant.io).

Roland Bende

This plugin adds a custom REST API endpoint that returns information about the current versions of the WordPress core, active themes, and active plugins.
Useful for remote WordPress site version monitoring & logging, CI/CD checks, and automated update workflows.
Both endpoints require authentication via a Bearer token.
Endpoint 1: Status — outdated items only
<ul>
<li>HTTP method: <code>GET</code></li>
<li>API endpoint: <code>/wp-json/vercheck-api/v1/status</code></li>
</ul>
Returns only items that have available updates: 
– WordPress core update status. 
– A list of plugins with available updates. 
– A list of themes with available updates.
Endpoint 2: Audit — full inventory
<ul>
<li>HTTP method: <code>GET</code></li>
<li>API endpoint: <code>/wp-json/vercheck-api/v1/audit</code></li>
</ul>
Returns a complete inventory of everything installed: 
– WordPress core version info. 
– All installed themes (active and inactive) with version and update info. 
– All installed plugins (active and inactive) with version and update info.
Example response — /v1/status:
<pre><code> {
 "core": {
 "current_version": "6.4.3",
 "new_version": "6.5",
 "is_outdated": true
 },
 "outdated_themes": [],
 "outdated_plugins": [
 {
 "name": "Example Plugin",
 "current_version": "1.2.0",
 "new_version": "1.3.0"
 }
 ]
 }
</code></pre>
Example response — /v1/audit:
<pre><code> {
 "core": {
 "current_version": "6.4.3",
 "new_version": "6.5",
 "is_outdated": true
 },
 "themes": [
 {
 "name": "Twenty Twenty-Four",
 "slug": "twentytwentyfour",
 "current_version": "1.3",
 "new_version": null,
 "is_outdated": false,
 "is_active": true
 }
 ],
 "plugins": [
 {
 "name": "Example Plugin",
 "slug": "example-plugin/example-plugin.php",
 "current_version": "1.2.0",
 "new_version": "1.3.0",
 "is_outdated": true,
 "is_active": true
 }
 ]
 }
</code></pre>
Additional info: 
The unique request ID for each API call is returned in the response header:
<pre><code>X-Request-ID: {{unique-request-id}}
</code></pre>

VerCheck API

A REST API endpoint for checking WordPress core, theme, and plugin versions.

Vigilant Healthchecks vs VerCheck API