Modules Insight
Modules Insight helps WordPress developers and site managers audit installed plugins, assess the risk of upgrading PHP and WordPress , and export complete reports — all from a single on-demand scan. What’s new in 4.0 WordPress upgrade risk — a second risk column alongside PHP, rated against a target
About this tool.
Modules Insight helps WordPress developers and site managers audit installed plugins, assess the risk of upgrading PHP and WordPress , and export complete reports — all from a single on-demand scan.
What’s new in 4.0
- WordPress upgrade risk — a second risk column alongside PHP, rated against a target WordPress version you choose (up to 7.1).
- PHP 8.5 added to the target-PHP selector.
- Send to Google Sheet — push the report straight into a spreadsheet via a Google Apps Script Web App you deploy once (no Google API keys stored in WordPress).
- Ask AI — for plugins the metadata can’t settle (Medium / High / Not on WP.org), ask a question and get an answer from the WordPress core AI Client. Requires WordPress 7.0+ with an AI provider configured under Settings → AI; the feature hides itself otherwise.
PHP Upgrade Risk Evaluator
Planning a server PHP upgrade? MI queries the WordPress.org API for each installed plugin and produces a colour-coded risk table showing how likely each plugin is to break on your target PHP version.
Each plugin is rated Low , Medium , High , or Not on WP.org based on two signals:
1. Last Updated — how recently the plugin received a release on WordPress.org. 2. Minimum PHP Declared — the Requires PHP field set by the plugin author.
Risk is assigned as follows:
- High — Not updated in over 3 years, or declares a minimum PHP below 7.0. These carry the greatest risk of breaking on PHP 8.x and should be investigated before upgrading.
- Medium — Falls between High and Low. Test on a staging environment before upgrading production.
- Low — Updated within the last 12–18 months and declares PHP 7.4 or higher as its minimum. Likely compatible, but a quick smoke test after upgrading is still recommended.
- Not on WP.org — Not found in the WordPress.org directory (premium plugins, custom code). Compatibility must be verified manually with the vendor.
Important: risk ratings are based on publicly available metadata, not code analysis. A Low-rated plugin could still have incompatibilities; a High-rated plugin might work perfectly. Use the table as a triage guide, not a guarantee. Always test on a staging environment before upgrading PHP on a live server.
Results from the WordPress.org API are cached per plugin for 24 hours to avoid unnecessary external requests.