mindtwo Monitoring
Collects infrastructure, package and security-audit data and reports it to the mindtwo monitoring dashboard — signed, scheduled, and pullable via /api/app-monitoring.
by mindtwo GmbH · github.com/mindtwo/wordpress-monitoring · website
★ 0stars
4composer installs
0forks
Install
No release zip yet. The repository archive installs, but the folder name will carry the branch suffix and updates will not flow:
wp plugin install https://github.com/mindtwo/wordpress-monitoring/archive/refs/heads/main.zipAlso on Packagist as mindtwo/wordpress-monitoring:
composer require mindtwo/wordpress-monitoringFrom the readme
mindtwo/wordpress-monitoring
WordPress plugin of the mindtwo monitoring suite. On top of
mindtwo/base-monitoring — which collects OS,
web server, database, Node.js, system stats, Composer/npm packages, security audits, licenses
and git status — this plugin adds:
- WordPress collectors — core version (matched against endoflife.date), installed plugins
and themes with versions, activity state and available updates, plus operational state
(environment type, debug flags, multisite, language).
- Push — a WP-Cron scheduled push of signed snapshots to the central endpoint.
- Pull — a signed GET /api/app-monitoring endpoint with rate limiting, optional IP
allow-listing and transient-cached snapshots.
- Settings screen — Settings → Monitoring, with the spec'd priority chain:
admin backend → MONITORING constants/environment variables → secure defaults.
Installation
Composer-based WordPress (Bedrock & co.)
Custom Composer setups (non-Bedrock)
If your project manages WordPress via Composer (e.g. johnpbloch/wordpress) but does not
load the project-root vendor/autoload.php globally, the plugin's classes are unavailable when
WordPress loads the plugin file. The result is silent: no
Read the full README on GitHub →
Releases
| Tag | Published |
|---|---|
| v1.0.0 | Aug 13, 2026 |
These releases are tags only. The author does not attach a packaged zip, so there are no download counts to report.