Title: Modules Insight Author: Pedro Matias (FroPT) Published: Avrigl 14, 2025 Last modified: Settember 4, 2026 --- Search plugins ![](https://ps.w.org/modules-insight/assets/icon-256x256.png?rev=3680023) # Modules Insight By [Pedro Matias (FroPT)](https://profiles.wordpress.org/fropt/) [Telechargiada](https://downloads.wordpress.org/plugin/modules-insight.4.0.2.zip) * [Details](https://roh.wordpress.org/plugins/modules-insight/#description) * [Reviews](https://roh.wordpress.org/plugins/modules-insight/#reviews) * [Installation](https://roh.wordpress.org/plugins/modules-insight/#installation) * [Development](https://roh.wordpress.org/plugins/modules-insight/#developers) [Support](https://wordpress.org/support/plugin/modules-insight/) ## Descripziun **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`, 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, 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. ## Maletgs dal visur [⌊The Modules Insight dashboard widget showing active/inactive plugins.⌉⌊The Modules Insight dashboard widget showing active/inactive plugins.⌉[ The Modules Insight dashboard widget showing active/inactive plugins. [⌊Example of a page generated using the shortcode and the collapsed description view using
.⌉⌊Example of a page generated using the shortcode and the collapsed description view using
.⌉[ Example of a page generated using the shortcode and the collapsed description view using `
`. [⌊The "Download List as JSON" button available to administrators and structure of the exported JSON file.⌉⌊The "Download List as JSON" button available to administrators and structure of the exported JSON file.⌉[ The „Download List as JSON“ button available to administrators and structure of the exported JSON file. [⌊Example of "print" page using shortcode and automatic expanded description view using
.⌉⌊Example of "print" page using shortcode and automatic expanded description view using
.⌉[ Example of „print“ page using shortcode and automatic expanded description view using `
`. ## Installaziun 1. Upload the `modules-insight` folder to the `/wp-content/plugins/` directory, or install through the WordPress plugin screen directly (Plugins > Add New). 2. Activate the plugin through the Plugins menu in WordPress. 3. Check your **Dashboard** for the „Modules Insight – Plugin List“ widget, or use the shortcode `[plugin_list]` on any page or post. 4. Press **Scan Plugins** to load the plugin list. 5. Pick your **Target PHP** and **Target WP** versions, then press **Check Upgrade Compatibility** to run the risk evaluation against the WordPress.org API. 6. Once the scan is complete, press **Download List as JSON**, **Download List as CSV**, or **Send report to Google Sheet** to export the full report, including the compatibility data. 7. Optionally, set up the Google Sheets export and (on WordPress 7.0+) the AI Q&A under **Settings Modules Insight**. ## FAQ ### 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 directory. Risk must be assessed manually. These are metadata signals, not a code scan. Always test on a staging environment before upgrading PHP on a live server. ### 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, 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. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Modules Insight” is open source software. The following people have contributed to this plugin. Contributors * [ Pedro Matias (FroPT) ](https://profiles.wordpress.org/fropt/) * [ Pedro Matias ](https://profiles.wordpress.org/pedro-matias/) [Translate “Modules Insight” into your language.](https://translate.wordpress.org/projects/wp-plugins/modules-insight) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/modules-insight/), check out the [SVN repository](https://plugins.svn.wordpress.org/modules-insight/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/modules-insight/) by [RSS](https://plugins.trac.wordpress.org/log/modules-insight/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 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-*` to `modules-insight-*` so WordPress actually loads them (the text domain is `modules-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. #### 3.1.3 * Fix: Screenshots and plugin icon now correctly deployed to the WordPress.org assets directory. #### 3.1.2 * Compat: Tested and confirmed compatible with WordPress 7.0. * Updated minimum requirements: WordPress 6.0+, PHP 8.0+. * Updated screenshots and plugin icon. * Plugin URI updated to https://aura-plugins.com. #### 3.1.1 * Docs: Rewrote plugin description and FAQ to lead with the PHP upgrade risk evaluator and document how risk is calculated. #### 3.1.0 * Feature: PHP Compatibility Checker — after a scan, a „Check PHP 8.3 Compatibility“ button queries the WordPress.org API for each plugin (last updated, minimum PHP required) and displays a colour-coded risk table (Low / Medium / High / Not on WP.org). Results are cached per plugin for 24 hours. * Feature: JSON and CSV exports now include the cached compatibility data (last updated, min PHP, risk level) for any plugin that has been checked. Exports without a prior check show „not_checked“. * Feature: Plugin assets now load on the admin dashboard as well as the frontend, enabling the compatibility checker inside the dashboard widget. #### 3.0.0 * Feature: Plugin data is now loaded on demand — a Scan button must be pressed before any data is retrieved. Nothing runs on page load automatically. * Perf: Plugin data is cached via transient (5 min) and auto-invalidated on plugin activate/deactivate/update and theme switch. * Perf: Replaced O(n) in_array() loop with O(1) array_flip()+isset() for active plugin lookups. * Perf: Cached is_single()||is_page() result before the plugin loop to avoid redundant calls per iteration. * Perf: Removed redundant wp_kses() pass in the dashboard widget — all output is already escaped at source. * Fix: Print CSS now correctly hides the download buttons wrapper (was targeting a stale selector). #### 2.9.9 * Feature: Report now includes WordPress version and active theme info (name, version, author, URI) in the HTML output and in both JSON and CSV exports. #### 2.9.8 * Feature: Added CSV export — administrators can now download the plugin list as a .csv file alongside the existing JSON export. #### 2.9.7 * Version bump. #### 2.9.6 * Version bump. #### 2.9.5 * Version bump. #### 2.9.4 * Version bump. #### 2.9.3 * Version bump. #### 2.9.2 * Fix: Remove duplicate nonce hidden field in the download form (wp_nonce_field() already outputs it). * Fix: JS print listener now only closes `
` elements that were auto-opened, preserving manually-opened ones. * Fix: Declare `elms` and `e` with `const` in the print media listener to avoid implicit globals. * Perf: Move `get_site_option('active_sitewide_plugins')` call outside the plugin foreach loop on multisite. * Security: Simplify shortcode capability check — remove `is_admin()` context check, rely solely on `activate_plugins`. * Perf: Register assets on `wp_enqueue_scripts` and enqueue them inside the shortcode, so they only load on pages using `[plugin_list]`. * Perf: Update asset version strings from 2.3.0 to 2.9.2 to ensure browsers pick up current files. * Accessibility: Replace `outline: none` on button focus with a visible `2px solid` outline. * Dev: Add `.vscode/settings.json` enabling Intelephense’s built-in WordPress stubs for accurate static analysis. #### 2.9.1 * Style: Added `fusion-tb-footer` and `fusion-footer` CSS classes to print hide rules for Avada theme compatibility. * Version bump for CSS and JS assets. #### 2.9.0 * Feature: Report header now shows site name, date, and URL when shortcode is rendered on a page or post. #### 2.8.0 * Fix: Corrected plugin GitHub URI to https://github.com/matias2018/Plugin-List- Display. #### 2.7.2 * Style: Added specific print-hide rules for Avada theme custom footer elements. #### 2.7.0 * Feature: Added informational message for users without the download capability. #### 2.6.0 * Feature: Enqueue JavaScript to auto-expand `
` elements when printing. #### 2.5.0 * Feature: Show plugin description inside `
`/`` when shortcode is rendered on a page or post. * Feature: Added `is_single()`/`is_page()` context check to conditionally show the description block. #### 2.4.0 * Feature: Added print styles to hide the download button, header, and footer when printing. #### 2.3.0 * Feature: Added network-active status display for multisite installs. #### 2.2.0 * Refine: Removed `
`/`` wrapper from description in default ( non-page) view. #### 2.1.2 * Fix: Use `current_time()` instead of `date()` for JSON filename timestamp to respect WordPress timezone settings (Fixes PHPCS error). #### 2.1.1 * Feature: Wrap plugin descriptions in `
`/`` tags for a cleaner default view. * Fix: Add required `translators:` comments for internationalization functions with placeholders (Fixes Plugin Check error). * Fix: Ensure `
` and `` tags are allowed in `wp_kses` for the dashboard widget. * Refine: Improve multisite plugin detection slightly. * Refine: Use case-insensitive sorting for plugin lists. #### 2.1.0 * Refactor: Introduce helper function `get_plugin_insight_data()` to centralize data retrieval. * Security: Regenerate plugin data on download instead of passing via POST. * Security: Add capability checks (`activate_plugins`) for viewing list and downloading JSON. * Security: Remove `nopriv` action hook for downloads. * Feature: Add more plugin details (version, description, author, URIs) to data structure. * Feature: Handle network-activated plugins on multisite installs. * Improvement: Use `wp_json_encode()` for standard JSON output. * Improvement: Use output buffering and proper escaping (`esc_*`, `wp_kses_post`) throughout HTML generation. * Improvement: Make widget title translatable. * Fix: Address various Plugin Check escaping errors. #### 2.0.2 * Initial version shared for review (contained shortcode, dashboard widget, basic JSON download via POST). #### 1.0.0 * (Internal/Previous Version) Initial concept release. ## Meta * Version **4.0.2** * Last updated **avant 2 dis** * Active installations **10+** * WordPress version ** 6.0 or higher ** * Tested up to **7.1** * PHP version ** 8.0 or higher ** * Language * [English (US)](https://wordpress.org/plugins/modules-insight/) * Tags * [Admin Tools](https://roh.wordpress.org/plugins/tags/admin-tools/)[developer-tools](https://roh.wordpress.org/plugins/tags/developer-tools/) [plugin management](https://roh.wordpress.org/plugins/tags/plugin-management/) [plugin status](https://roh.wordpress.org/plugins/tags/plugin-status/) * [Advanced View](https://roh.wordpress.org/plugins/modules-insight/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/modules-insight/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/modules-insight/reviews/) ## Contributors * [ Pedro Matias (FroPT) ](https://profiles.wordpress.org/fropt/) * [ Pedro Matias ](https://profiles.wordpress.org/pedro-matias/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/modules-insight/)