Icedor Johansson

WordPress warns about inactive plugins because they can pose security risks if left outdated. Icey – WP Plugin Archive Manager helps you mitigate this by moving inactive plugins to a secure archive folder, keeping them isolated from WordPress while still available for later use.
With a dedicated admin tab, you can easily restore archived plugins whenever needed—without cluttering your active plugin list or compromising security.
<h3>Localization</h3>
<ul>
<li>English (default)</li>
<li>Swedish (<code>sv_SE</code>)</li>
</ul>

Icey – Extension archiver

Securely archive inactive plugins to prevent security risks and avoid WordPress warnings. Restore anytime with a single click.

Pedro Matias

Modules Insight helps WordPress developers and site managers audit installed plugins, assess the risk of upgrading PHP, and export complete reports — all from a single on-demand scan.
<h3>PHP Upgrade Risk Evaluator</h3>
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 <code>Requires PHP</code> field set by the plugin author.
Risk is assigned as follows:
<ul>
<li>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.</li>
<li>Medium — Falls between High and Low. Test on a staging environment before upgrading production.</li>
<li>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.</li>
<li>Not on WP.org — Not found in the WordPress.org directory (premium plugins, custom code). Compatibility must be verified manually with the vendor.</li>
</ul>
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.
<h3>Plugin List and Reports</h3>
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 <code>.json</code> or <code>.csv</code>. Both formats include the PHP compatibility data if a check has been run prior to export.
Tested and fully compatible with WordPress 7.0.
<h3>Key Features</h3>
<ul>
<li>PHP upgrade risk evaluation via the WordPress.org API</li>
<li>Colour-coded risk table: Low / Medium / High / Not on WP.org</li>
<li>Lists all installed plugins with status, version, author, and URIs</li>
<li>Reports WordPress version and active theme</li>
<li>Export as JSON or CSV (includes compat data when available)</li>
<li>Dashboard widget and <code>[plugin_list]</code> shortcode</li>
<li>Scan-on-demand — nothing runs automatically on page load</li>
<li>100% read-only — safe for production use</li>
</ul>
<h3>Use Cases</h3>
<ul>
<li>Assessing risk before upgrading PHP on a server</li>
<li>Managing multiple WordPress sites and keeping plugins audited</li>
<li>Client-facing reports on installed plugins</li>
<li>Pre-deployment or pre-update plugin audits</li>
</ul>
<h3>Credits</h3>
Made with ❤️ by Pedro Matias for WordPress developers and admins.

Modules Insight

Audit installed plugins, assess PHP upgrade risk via the WordPress.org API, and export full reports as JSON or CSV.

Icey – Extension archiver vs Modules Insight