Problem
Plugin health data (repository status, last update, tested-up-to version) currently only lives on a separate report page. Admins don't see this information where they actually manage plugins — the native Plugins list table.
Proposed changes
Add columns to the Plugins page
Hook into WordPress core's plugin list table via manage_plugins_columns and manage_plugins_custom_column to show:
- Repository — wordpress.org / closed / self-hosted host name
- Last Update — human-readable time diff with color coding
- Tested up to — WP version with color coding
Inline warnings
Use after_plugin_row to show full-width warning rows beneath problematic plugins:
- Plugin closed on wordpress.org → red warning
- Not updated in >2 years → yellow warning
- Not tested with current WP major version → yellow warning
Data strategy
- If cached data exists (from report page visit) → show immediately
- If no cache → show "—" (don't trigger API calls on every plugin list page load)
Multisite
Hooks into manage_plugins-network_columns / manage_plugins-network_custom_column for network admin.
Problem
Plugin health data (repository status, last update, tested-up-to version) currently only lives on a separate report page. Admins don't see this information where they actually manage plugins — the native Plugins list table.
Proposed changes
Add columns to the Plugins page
Hook into WordPress core's plugin list table via
manage_plugins_columnsandmanage_plugins_custom_columnto show:Inline warnings
Use
after_plugin_rowto show full-width warning rows beneath problematic plugins:Data strategy
Multisite
Hooks into
manage_plugins-network_columns/manage_plugins-network_custom_columnfor network admin.