Upgrade Readiness Monitor

Description

Upgrade Readiness Monitor tells you whether a site is safe to upgrade before you bump PHP or WordPress — and exactly what to fix if it isn’t.

It works in three complementary ways:

• Real-time deprecation capture. The plugin listens for WordPress’s deprecation signals (deprecated_function_run, deprecated_hook_run, doing_it_wrong_run, and friends) as your site runs. Because those signals fire regardless of WP_DEBUG, you catch real deprecations on production without turning on debug mode — each one attributed to the plugin or theme that triggered it.

• Plugin & theme audit. A one-click scan checks every installed plugin and your active theme against WordPress.org for abandoned code (no update in 2+ years), “tested up to” lag, available updates, and declared PHP requirements.

• Static code scan against your chosen target. Every plugin and theme — including custom and premium code that isn’t on WordPress.org — has its PHP parsed and checked against the WordPress and PHP versions you plan to upgrade to. Findings are graded Error (will break — e.g. a function removed in the target PHP version) or Warning (a deprecation notice you’ll start seeing). The functions the target WordPress version deprecates are read from WordPress core itself, so results reflect the actual upgrade.

Everything rolls up into a single green / amber / red readiness verdict, and a target selector lets you choose exactly which WordPress and PHP versions you’re upgrading to.

Built for developers and agencies

• No configuration — install, choose your target, and scan.
• Read-only and safe: it never changes your site.
• The audit runs in the background in small chunks, so it never blocks or slows a page load.
• WP-CLI included: wp readiness check prints the full report and exits non-zero on a red verdict, so you can gate upgrades in CI/staging.

WP-CLI

# Full readiness report
wp readiness check

# Machine-readable output for pipelines
wp readiness check --format=json

External services

This plugin connects to WordPress.org to assess upgrade readiness. It does not contact any other third-party service and does not send any personal data.

1. WordPress.org Plugins/Themes API (api.wordpress.org) — for each installed plugin and theme, its slug is sent to look up the latest version, “tested up to” value, and last-updated date. Used during a scan and the weekly background scan.
2. WordPress.org version list (api.wordpress.org/core/stable-check) — fetches the list of available WordPress versions to populate the upgrade-target selector.
3. WordPress.org core source (core.svn.wordpress.org) — downloads the target WordPress version’s public list of deprecated functions to compare against your code. Only the version number is part of the request.

All three are WordPress.org services, governed by the WordPress.org privacy policy (https://wordpress.org/about/privacy/).