WordPress Plugin

Know which of your plugins are quietly dying.

ExtensionLifeCheck scans your installed WordPress plugins for abandonment risk — outdated, untested, or unmaintained — and suggests actively maintained alternatives from WordPress.org.

What it does

Read-only, privacy-friendly, and powered entirely by WordPress core APIs.

Scans every plugin

Reads your installed plugins with native WordPress functions only — nothing is changed, deactivated, or deleted.

Flags real risk

Compares each plugin against the official WordPress.org API for last update, version gap, and compatibility.

Suggests alternatives

Recommends one to three actively maintained WordPress.org replacements for plugins that need review.

Exports a report

Download a one-click CSV audit of your latest scan to share with clients or your team.

Safe Low Medium High Critical Unknown

How it works

Three steps, entirely inside your wp-admin.

Privacy first

No tracking. No personal data. No front-end requests.

Local only

The plugin runs only inside wp-admin when an administrator starts a scan.

Official API

It connects solely to api.wordpress.org to read public plugin metadata.

Cached

Responses are cached in WordPress transients for 12 hours to limit external requests.

No personally identifiable information is ever sent. ExtensionLifeCheck does not add anything to the front end of your site and never modifies, deactivates, or removes plugins.

Frequently asked questions

 

Will this change or remove my plugins?

No. ExtensionLifeCheck is strictly read-only. It does not deactivate, update, delete, or modify any plugin.

Why is a plugin marked as “Unknown”?

Unknown usually means the plugin is not in the WordPress.org directory (premium, custom, or privately hosted) or that WordPress.org could not be reached during the scan.

How are alternatives chosen?

It searches WordPress.org for closely related plugins, then filters for recent updates, current compatibility, and meaningful active install counts.

Will this slow down my site?

No. No visitor-facing requests are added. Scans run only in wp-admin and API responses are cached with transients.