Modules Insight
Audit plugins, rate PHP and WordPress upgrade risk from the WordPress.org API, and export to JSON, CSV, Excel, or a Google Sheet.
Solid choice
Modules Insight is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites and was last updated 3 weeks ago, and scores 66/100 on our health check.
- Actively developed — last update 3 weeks ago
- Tested with the latest WordPress (7.1)
- Small user base (10+ active installs)
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Modules Insight stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| Admin Tools | >100 |
| developer-tools | >100 |
| plugin management | >100 |
| plugin report | >100 |
| plugin status | >100 |
Version adoption
Share of active sites per release.
About Modules Insight
From the official readme · v4.0.4Description
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.
Plugin List and Reports
MI lists all installed plugins (active, inactive, and network-active on multisite) with version numbers, author details, and descriptions. It also reports the active WordPress version and active theme.
Reports can be exported as .json, .csv, .xlsx (best for Excel Online / SharePoint), or sent to a Google Sheet. All include the PHP and WordPress compatibility data if a check has been run prior to export.
Tested and fully compatible with WordPress 7.1.
WordPress Upgrade Risk Evaluator
The same check now rates each plugin against a target WordPress version too (selectable, up to 7.1). The signal is the plugin’s “Tested up to” value on WordPress.org combined with how recently it was updated: a plugin tested at or beyond your target is Low, one release behind and freshly updated is Low, several releases behind or long-stale is High. As with the PHP rating, this is a metadata signal, not a code scan — always test on staging.
Key Features
- PHP and WordPress upgrade risk evaluation via the WordPress.org API
- Two colour-coded risk columns: Low / Medium / High / Not on WP.org
- Selectable targets: PHP 8.0–8.5, WordPress 6.7–7.1
- Lists all installed plugins with status, version, author, and URIs
- Reports WordPress version and active theme
- Export as JSON, CSV, Excel (.xlsx), or straight to a Google Sheet (includes compat data when available)
- Ask AI about a specific plugin using the WordPress core AI Client (WordPress 7.0+, optional)
- Dashboard widget and
[plugin_list]shortcode - Scan-on-demand — nothing runs automatically on page load
- Read-only against your site — the only writes are the report rows you send to your own Google Sheet
External services
Modules Insight makes outbound requests only when an administrator asks it to:
- WordPress.org plugin API (api.wordpress.org) — during a compatibility check, to read each plugin’s last-updated date, “tested up to” and “requires PHP” values. Cached per plugin for 24 hours.
- Your Google Apps Script Web App — only if you configure the Google Sheets export, and only when you press Send report to Google Sheet. The plugin POSTs the report rows plus your shared secret token to the URL you provide.
- Your site’s AI provider — only if you use Ask AI. The request goes through the WordPress core AI Client to whichever provider your site admin configured under Settings → AI. The plugin name, version, description, its WordPress.org metadata, your risk ratings and (if present) the plugin’s own readme.txt are sent as context.
Use Cases
- Assessing risk before upgrading PHP or WordPress on a server
- Managing multiple WordPress sites and keeping plugins audited
- Client-facing reports on installed plugins, collected in a shared Google Sheet
- Pre-deployment or pre-update plugin audits
Credits
Made with ❤️ by Pedro Matias for WordPress developers and admins.
Installation
- Upload the
modules-insightfolder to the/wp-content/plugins/directory, or install through the WordPress plugin screen directly (Plugins > Add New). - Activate the plugin through the Plugins menu in WordPress.
- Check your Dashboard for the “Modules Insight – Plugin List” widget, or use the shortcode
[plugin_list]on any page or post. - Press Scan Plugins to load the plugin list.
- Pick your Target PHP and Target WP versions, then press Check Upgrade Compatibility to run the risk evaluation against the WordPress.org API.
- Once the scan is complete, press Download List as JSON, Download List as CSV, Download List as Excel, or Send report to Google Sheet to export the full report, including the compatibility data.
- Optionally, set up the Google Sheets export and (on WordPress 7.0+) the AI Q&A under Settings → Modules Insight.
Frequently asked questions
How is the PHP upgrade risk calculated?
Risk is based on two signals pulled from the WordPress.org plugin directory for each plugin: 1. Last Updated — how recently the plugin received a published release. 2. Minimum PHP Declared — the Requires PHP value the author set on WordPress.org. The rating is assigned as follows: High — Not updated in over 3 years, OR declares a minimum PHP below 7.0. Investigate before upgrading. Low — Updated within 12–18 months AND declares PHP 7.4 or higher as its minimum. Medium — Anything between High and Low. Test on staging before upgrading production. Not on WP.org — Plugin not found in the…
Why is my recently-updated plugin showing as Medium instead of Low?
The most common reason is that the plugin’s Requires PHP field on WordPress.org is set below 7.4 — even if the plugin runs perfectly on modern PHP. Authors often set this conservatively and forget to update it. In this case Medium does not mean the plugin is broken; it means the metadata is incomplete. Check the plugin’s own changelog or test directly on staging.
What does “Not on WP.org” mean in the risk table?
The plugin was not found in the WordPress.org directory. This is normal for premium plugins (WooCommerce extensions, page builder add-ons, etc.) and custom-built plugins. Their compatibility cannot be assessed automatically — check with the vendor or test directly on a staging environment running the target PHP version.
Are the risk ratings a guarantee?
No. They are a triage guide based on publicly available metadata. A Low-rated plugin could still have incompatibilities; a High-rated plugin might work perfectly. The table helps you decide where to focus your testing effort, not whether to skip testing altogether.
Does this plugin make any changes to my site?
No. MI does not activate, deactivate, install, or delete any plugins, and it never modifies your site’s data. The only write it performs anywhere is appending report rows to a Google Sheet you configure — and only when you press Send report to Google Sheet.
How does the Google Sheets export work? Do I need a Google Cloud account?
No Google Cloud project, no API keys. You create a normal Google Sheet, add a short Google Apps Script (provided on the settings page) and deploy it as a Web App. You then paste that Web App URL and a shared secret token into Settings → Modules Insight. The plugin POSTs the report to your script, which appends the rows. The token is stored in your database (or a wp-config.php constant) and is never shown again after saving.
What does “Ask AI” need?
WordPress 7.0 or newer (the AI Client ships in core from 7.0), with an AI provider (Anthropic, Google, or OpenAI) configured by an administrator in your site’s AI settings. Modules Insight uses the core AI Client — it stores no API keys of its own. If no provider can serve a request, the “Ask AI” button doesn’t appear and the settings page explains why. If the “Connector Approvals” experiment is enabled, an administrator must approve Modules Insight after its first request. Answers are cached for 12 hours per question to limit provider costs.
Who can see the plugin list and run the compatibility check?
Only users with the activate_plugins capability (typically Administrators). The settings page requires manage_options.
What formats can I export?
JSON, CSV, Excel, or a Google Sheet. All include the PHP and WordPress compatibility data (last updated, “tested up to”, minimum PHP, both risk levels) for any plugin that has been checked. Plugins not yet checked show not_checked in those fields.
Can I use this on a live/production site?
Yes. MI loads no assets unless an admin explicitly presses Scan, and makes no outbound requests except the admin-initiated ones listed under “External services” above.
Changelog
Adds a native Excel (.xlsx) export for Excel Online / SharePoint and fixes accented names in the CSV export.
4.0.4
- Feature: “Download List as Excel (for SharePoint)” — a native
.xlsxexport. It opens with real columns and correct UTF-8 text in Excel, Excel Online and SharePoint, where CSV delimiter and encoding detection is unreliable. Written in-plugin; no library or PHP zip extension required. - Fix: The CSV export now begins with a UTF-8 BOM, so Excel stops mangling accented author names after the download loses its charset header.
4.0.2
- Fix: “Send report to Google Sheet” failed with “The Google Sheet rejected the request: HTTP 200”. The Apps Script Web App replies with a 302 to script.googleusercontent.com, an endpoint that only accepts GET; WordPress re-issued the redirect as POST and never received the JSON reply. The plugin now follows the redirect with a GET.
- Fix: The report’s spacer row is no longer an empty array — Apps Script’s appendRow() rejects one, which could fail the whole push. The bundled Apps Script also guards against it.
- Change: “Send report to Google Sheet” now warns when upgrade compatibility has not been checked yet, so you don’t push a report whose risk columns all read “not_checked”.
- Fix: A single failed plugin lookup during “Check Upgrade Compatibility” no longer aborts the whole run — the remaining plugins are still checked and the progress line reports how many failed. Row updates also tolerate an unexpected table layout instead of throwing.
4.0.0
- Feature: WordPress upgrade risk — a second risk column, rated against a selectable target WordPress version (6.7–7.1), derived from each plugin’s “Tested up to” value and last-updated age.
- Feature: PHP 8.5 added to the target-PHP selector.
- Feature: Send report to Google Sheet — push the full report into a spreadsheet via a Google Apps Script Web App you deploy once. No Google API keys are stored in WordPress. Configured under Settings → Modules Insight.
- Feature: Ask AI — for plugins rated Medium / High / Not on WP.org, ask a free-text question and get an answer from the WordPress core AI Client (WordPress 7.0+ with a provider configured under Settings → AI). Answers cached 12 hours.
- Change: The compatibility check now covers both PHP and WordPress in one pass; the button is relabelled “Check Upgrade Compatibility”.
- Change: JSON and CSV exports gain the WordPress risk column and record both selected targets. CSV cell values starting with = + – @ are now prefixed to prevent spreadsheet formula injection.
- Change: Asset cache-busting is tied to the plugin version again (was pinned at 3.2.0).
- Fix: Translation files renamed from
modules_insight-*tomodules-insight-*so WordPress actually loads them (the text domain ismodules-insight). - Fix: Compatible with WordPress 7.1; README requirements corrected to WordPress 6.0 / PHP 8.0.
- Dev: Code split into
includes/(settings, google-sheets, ai).
3.2.2
- Fix: Compat table no longer overflows the dashboard widget — wrapped in a horizontally scrollable container.
- Fix: “Tested up to (WP)” now always reflects fresh data — stale transients built before 3.2.0 are ignored and re-fetched automatically.
- Fix: Plugin icon now shown in the dashboard widget title bar.
3.2.1
- Fix: Renamed icon-265×256.png to icon-256×256.png so WordPress.org recognises and displays the plugin icon correctly.
- Updated plugin icons (128×128 and 256×256).
3.2.0
- Feature: Target PHP version selector — choose PHP 8.0 through 8.4 before running the compatibility check. Risk thresholds shift with the selected version.
- Feature: “Tested up to (WP)” is now fetched from WordPress.org and shown as a third signal. An age-driven High rating is softened to Medium when the plugin declares compatibility with a recent WordPress version (6.3+), suggesting the author is actively maintaining it.
- Export: JSON and CSV exports now include the “Tested up to (WP)” field and reflect the selected target PHP version in the risk column header.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Modules Insight alternatives
All Admin Tools plugins →
FAQ
Modules Insight: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 30, 2026
Is Modules Insight free?
Yes. Modules Insight is free to download and use from the official WordPress.org plugin directory.
Is Modules Insight safe to use in 2026?
Modules Insight is a solid plugin choice in 2026, with a few things worth checking first. It runs on 10+ sites and was last updated 3 weeks ago, and scores 66/100 on our health check.
How many websites use Modules Insight?
Modules Insight is active on 10+ WordPress websites and has been downloaded 1,232 times since it launched in April 2025. It was downloaded 252 times in the last 30 days.
Does Modules Insight work with WordPress 7.1?
Yes. The developer has tested Modules Insight up to WordPress 7.1.2, the latest release. It requires WordPress 6.0 or newer.
What PHP version does Modules Insight need?
Modules Insight requires PHP 8.0 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Modules Insight last updated?
The latest version, 4.0.4, was released on September 10, 2026 (3 weeks ago).
Who makes Modules Insight?
Modules Insight is developed and maintained by Pedro Matias (FroPT).
What are the best alternatives to Modules Insight?
The most popular alternatives to Modules Insight are Admin Tools (3K+ installs), Cron Jobs (2K+ installs) and WP Extended (600+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
