Upaccn PHP Upgrade Risk Audit helps you answer one practical question before changing PHP on a WordPress site: which installed plugin or theme could block this upgrade?
Choose a target PHP version, select the components you want to inspect, and run a local static-analysis scan. Results are grouped by plugin or theme and summarized as Ready, Review, or Blocked, with the relevant file, line, compatibility rule, and finding available for technical review.
Highlights
- Scan installed plugins and themes against a selected PHP 8.x target.
- Runs locally inside WordPress. Source code is not uploaded to an external scanning service.
- Does not require
exec(),shell_exec(),proc_open(), Composer, or command-line access on the host. - Read-only: the plugin never edits the code it scans.
- Bounded AJAX batches reduce the risk of one long blocking web request.
- Clear per-component Ready / Review / Blocked verdicts.
- Technical findings include file, line, severity, rule, and message.
- Bundled vendor-code findings are identified separately.
- The checker excludes itself from scan targets to avoid self-referential findings from its bundled analysis engine.
Important limitation
Static analysis can identify known PHP compatibility patterns, but it cannot execute every runtime path and cannot guarantee that a site will work perfectly after an upgrade. Always validate the final PHP change on staging before changing production.
Privacy
Scanning and scan state stay on the WordPress installation. Upaccn PHP Upgrade Risk Audit does not upload plugin or theme source code and does not include telemetry in this version.