Title: Plugevity Health Score
Author: plugevity
Published: <strong>November 15, 2026</strong>
Last modified: November 15, 2026

---

Search plugins

![](https://ps.w.org/plugevity-health-score/assets/banner-772x250.png?rev=3803137)

![](https://ps.w.org/plugevity-health-score/assets/icon.svg?rev=3803137)

# Plugevity Health Score

 By [plugevity](https://profiles.wordpress.org/plugevity/)

[Download](https://downloads.wordpress.org/plugin/plugevity-health-score.0.2.0.zip)

 * [Details](https://wordpress.org/plugins/plugevity-health-score/#description)
 * [Reviews](https://wordpress.org/plugins/plugevity-health-score/#reviews)
 *  [Installation](https://wordpress.org/plugins/plugevity-health-score/#installation)
 * [Development](https://wordpress.org/plugins/plugevity-health-score/#developers)

 [Support](https://wordpress.org/support/plugin/plugevity-health-score/)

## Description

WordPress tells you when an update is available. It does not tell you that a plugin
has not shipped a release in three years, that WordPress.org closed it for a security
issue, or that someone else now owns it.

Health Score checks every installed plugin and your active theme against public 
WordPress.org data once a day and gives each one a 0–100 longevity score with plain
reasons.

#### Features

 * **Longevity score** for every plugin and the active theme: last release, “tested
   up to” compared with the latest WordPress, and support-forum resolution rate.
 * **Closed plugin detection**: see at once when WordPress.org has closed a plugin
   you use, and why.
 * **Ownership-change alert**: Health Score remembers who owns each plugin on WordPress.
   org and emails you when that changes. When a plugin is sold, the new owner can
   ship any code in the next update; review it before you update.
 * **Site Health tests** for closed plugins, unreviewed ownership changes and plugins
   with no release in two years.
 * **Email alerts** only when something changes, plus an optional weekly summary.
 * **Works with AI assistants** (WordPress 6.9+): with the MCP Adapter plugin, an
   assistant can answer “which of my plugins should I worry about?” or “is this 
   plugin still maintained?” from the scores and reasons. The same read-only abilities(`
   plugevity/get-plugin-health` and `plugevity/list-risky-plugins`) are available
   to automations over the REST API.
 * Read-only: it never deactivates, updates or changes another plugin.

#### Replayed on a real case

In April 2026 WordPress.org closed 31 plugins after the buyer of a plugin portfolio
shipped a backdoor in their updates. We replayed the public history of those plugins
through Health Score: its first email, about the change of contributors, would have
gone out about 12 weeks before the backdoored version shipped. Health Score does
not read plugin code and never blocks an update; what to do with the warning is 
up to you. Method and results: https://plugevity.com/cases/essential-plugin-backdoor/

The six signs it reads, and what to do about each one: https://plugevity.com/blog/
how-to-tell-if-a-wordpress-plugin-is-abandoned/

#### Privacy

Health Score sends no data to Plugevity. Once a day, in the background, it asks 
the public WordPress.org API (api.wordpress.org) about each installed plugin and
the active theme, sending only their slugs. WordPress itself sends the same list
to the same service when it checks for updates. Plugins whose `Update URI` points
outside WordPress.org are never sent. Alert emails go from your own site to the 
address you choose.

If you connect an AI assistant to your site with the MCP Adapter plugin, using a
user who can manage plugins, that assistant can read the list of installed plugins
and the active theme with their scores and reasons. Health Score does not send this
anywhere by itself; the assistant only gets it when it asks.

“Copy diagnostics” on the Health Score screen builds an anonymous summary (versions,
settings and counts) you can paste in a support topic. The plugin does not send 
it anywhere.

#### Built to last

Plugevity plugins follow a public continuity pledge: https://plugevity.com/pledge/

## Screenshots

[⌊The Health Score screen: changes to review, and a score with plain reasons for
every plugin and the active theme.⌉⌊The Health Score screen: changes to review, 
and a score with plain reasons for every plugin and the active theme.⌉[

The Health Score screen: changes to review, and a score with plain reasons for every
plugin and the active theme.

[⌊Site Health flags an active plugin that WordPress.org closed and an ownership 
change to review.⌉⌊Site Health flags an active plugin that WordPress.org closed 
and an ownership change to review.⌉[

Site Health flags an active plugin that WordPress.org closed and an ownership change
to review.

[⌊Email alerts, and "Copy diagnostics" for support topics: you see what is copied,
and nothing is sent.⌉⌊Email alerts, and "Copy diagnostics" for support topics: you
see what is copied, and nothing is sent.⌉[

Email alerts, and “Copy diagnostics” for support topics: you see what is copied,
and nothing is sent.

## Installation

 1. Install the plugin from Plugins > Add New, or upload the ZIP.
 2. Activate it. The first check runs in the background within a minute or two.
 3. Go to Plugins > Health Score.

## FAQ

### How do I know if a WordPress plugin is abandoned?

Look at three things on its WordPress.org page: the date of the last release, the“
tested up to” WordPress version and whether the plugin is still listed. Health Score
reads the same public data for every plugin on your site once a day and turns it
into a 0 to 100 score with plain reasons, so you do not have to check each page 
by hand.

### What happens when a WordPress plugin changes owner?

The new owner can ship any code in the next update, and your site installs it like
any other update. WordPress does not tell you about the change. Health Score records
who owns each plugin on WordPress.org and emails you when that changes, so you can
review the next update before installing it.

### What does it mean when a plugin is closed on WordPress.org?

A closed plugin gets no more updates through WordPress.org, often because of an 
unfixed security issue or a guideline violation. WordPress does not warn you about
it in the dashboard. Health Score shows closed plugins with a score of 0 and the
closure reason, and adds a Site Health test for them.

### Does it slow down my site?

No. All requests to WordPress.org run in WP-Cron, in small batches, never while 
a page loads. The screen, Site Health and the abilities read cached results.

### Why is a plugin “Not checked”?

It is not hosted on WordPress.org (for example a premium plugin), its updates come
from elsewhere (`Update URI`), or a different product uses the same slug on WordPress.
org. There is no public data to score it with.

### How is the score calculated?

It starts at 100. A release older than six months, one year or two years, a “tested
up to” version two or more releases behind the latest WordPress, a very low support
resolution rate and an unreviewed ownership change each subtract points. A closed
plugin scores 0. Every deduction is shown as a reason.

### I got an ownership alert. What now?

Check the plugin’s page and changelog on WordPress.org and who the new owner is.
If you trust the change, click Acknowledge on the Health Score screen. Contributor
list changes are reported separately and count less.

### Can an AI assistant tell me which plugins are risky?

Yes, from WordPress 6.9. Install the MCP Adapter plugin from WordPress.org and connect
your assistant with a user who can manage plugins. It can then read the scores and
reasons and answer questions such as “which of my plugins should I worry about first?”,“
did any plugin change owner?” or “which plugins have had no release in years?”. 
It reads the results of the last daily check; it cannot change, deactivate or update
anything through Health Score, and it is not a vulnerability scan.

### What does “Copy diagnostics” include?

Your WordPress and PHP versions, the plugin’s settings as yes/no values, how many
plugins are installed and active, how many got each grade, and how many ownership
or closure alerts are open or acknowledged. It never includes your site address,
emails, user names, or the names or slugs of your plugins and theme. Click “Show
what will be copied” to see it before copying. Nothing is sent by the plugin.

### WP-Cron is disabled on my site.

Run WP-Cron from a system cron job, otherwise checks never run. The screen shows
when the last check finished.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Plugevity Health Score” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ plugevity ](https://profiles.wordpress.org/plugevity/)
 *   [ leonardo picciani ](https://profiles.wordpress.org/picciani/)

[Translate “Plugevity Health Score” into your language.](https://translate.wordpress.org/projects/wp-plugins/plugevity-health-score)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/plugevity-health-score/),
check out the [SVN repository](https://plugins.svn.wordpress.org/plugevity-health-score/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/plugevity-health-score/)
by [RSS](https://plugins.trac.wordpress.org/log/plugevity-health-score/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.2.0

 * New: AI assistants connected through the MCP Adapter plugin (WordPress 6.9+) 
   can read the scores and reasons, to answer questions such as “which of my plugins
   should I worry about?” or “is this plugin still maintained?”. Read-only, from
   the last daily check.
 * New: the `plugevity/get-plugin-health` ability returns a count per grade, and`
   plugevity/list-risky-plugins` returns the time of the last check.
 * Improved: ability descriptions say what each one answers and what it is not (
   not a vulnerability scan).
 * New filter `plugevity_plugin_health_mcp_public` to keep an ability out of MCP.

#### 0.1.0

 * First release.

## Meta

 *  Version **0.2.0**
 *  Last updated **1 day ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.5 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 7.4 or higher **
 * Tags
 * [abandoned plugins](https://wordpress.org/plugins/tags/abandoned-plugins/)[maintenance](https://wordpress.org/plugins/tags/maintenance/)
   [plugins](https://wordpress.org/plugins/tags/plugins/)[security](https://wordpress.org/plugins/tags/security/)
   [site health](https://wordpress.org/plugins/tags/site-health/)
 *  [Advanced View](https://wordpress.org/plugins/plugevity-health-score/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/plugevity-health-score/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/plugevity-health-score/reviews/)

## Contributors

 *   [ plugevity ](https://profiles.wordpress.org/plugevity/)
 *   [ leonardo picciani ](https://profiles.wordpress.org/picciani/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/plugevity-health-score/)