All Modules LITE & PRO

Blast Radius Analyzer

Maps the full footprint of every WordPress plugin and theme — custom database tables, cron jobs, REST routes, and hooks — before you make any changes.

  • Full Plugin Footprint Map
  • 0 Database Writes
  • Read-Only Architecture

What This Module Does

Before you deactivate a plugin, update a theme, or change a hosting environment, you need to understand what that plugin actually owns. The Blast Radius Analyzer maps every custom database table, cron job, REST API route, and hooked callback that plugins and themes have registered — so you can make changes with full awareness of all the dependencies involved.

Features at a Glance

Custom Database Tables

Lists every database table not part of WordPress core, attributed to the most likely responsible plugin or theme. Includes row count and size so you understand the data footprint before deactivating anything.

Third-Party Cron Jobs

Every scheduled event registered outside WordPress core is listed with its next run time, recurrence interval, and hook name — showing exactly which plugins are adding background tasks.

REST API Map

A complete list of every registered WordPress REST API route — including core routes and every plugin-added endpoint — color-coded by HTTP method (GET, POST, PUT, DELETE, PATCH) for instant visibility into your full API surface area.

Full Hook Inspector

Dumps the live $wp_filter global showing every registered action and filter, the callbacks attached, their priorities, and which plugin registered them. Available in a dark-mode modal with a pop-out view for deep inspection.

Why It Matters

  • Understand what a WordPress plugin truly owns before you deactivate or delete it
  • Audit your WordPress REST API exposure — see exactly which endpoints are publicly accessible
  • Trace unexpected WordPress site behaviour to specific hook registrations without guesswork
  • Document a site's complete plugin footprint for client handoffs or WordPress migrations
  • Identify plugins that left behind custom database tables after WordPress uninstallation

Frequently Asked Questions

How does the plugin attribute custom tables to specific plugins?

It uses table name prefix matching. Most plugins prefix custom tables with a short identifier (e.g. wc_ for WooCommerce). The analyzer matches these against known plugin patterns and active plugin slugs.

Is the Hook Inspector safe to use on a live production WordPress site?

Yes. The Hook Inspector reads the in-memory $wp_filter array that WordPress has already constructed for the current request. It does not trigger any hooks or modify any callbacks.

What's the difference between Lite and Pro for this module?

Lite shows the custom database tables list and cron job inventory. Pro unlocks the full REST API Map with HTTP method color-coding and the Hook Inspector with modal and pop-out view.

Can I use this to find what's causing a WordPress REST API conflict?

Yes — the REST API Map shows the namespace, route pattern, and HTTP methods for every registered endpoint, making it straightforward to identify route conflicts or unexpectedly public endpoints.

Know What Every WordPress Plugin Owns Before You Touch Anything

The complete picture of your WordPress installation's plugin footprint — in seconds, with zero risk.

Get Full Pro Access

Pro unlocks the full REST API Map with HTTP method color-coding and the Hook Inspector with modal and pop-out view.

Get Pro Now

Try the Free Lite Version

Lite includes the custom database tables list and cron job inventory — completely free, no account required.

Download Lite — Free