Konfyra Omni Guard

The problem Omni Guard solves:

Prevents WordPress White Screen of Death from missing plugin dependencies. Static scanner, runtime guard, pre-flight checks. Free.

This happens constantly. WordPress has no built-in protection for it. Omni Guard fills that gap.

How it works — four layers of protection:

1. Static Scanner
Analyses the PHP source code of all active plugins using PHP’s tokeniser (no regex, no exec). Builds a dependency map: which plugin calls functions defined in which other plugin. Runs twice daily via WP-Cron and whenever a plugin is activated or deactivated.

2. Runtime Error Handler
Registers a set_error_handler() and register_shutdown_function() at priority 1, before any other plugin fires. If an undefined function call occurs at runtime, Omni Guard catches it, logs the incident, and — in admin — shows a clean recovery page instead of a blank screen.

3. Dependency Pre-flight Check
On every admin request, reads the dependency map and verifies that every mapped cross-plugin function actually exists right now. If any is missing, an admin notice fires before any plugin code tries to call it.

4. Developer Safety Shims — og_call(), og_exists(), og_guard()
Global helper functions that plugin developers can use to make their cross-plugin calls crash-proof:

`php

// Returns WP_Error if missing — never crashes
$result = og_call( ‘some_plugin_function’, $arg1, $arg2 );

// Boolean existence check
if ( og_exists( ‘some_plugin_function’ ) ) { … }

// Call with a fallback
$result = og_guard( ‘some_plugin_function’, fn() => ‘default’, $arg1 );
`

Admin Dashboard includes:
* Live dependency health overview with KPI cards
* Full dependency map (filterable by risk level: high / medium / low)
* Incident log with detection method, timestamp, URL, and alert status
* Pre-flight status: functions missing right now
* Settings: scan depth, email alerts, whitelist, ignore list, danger zone

Email alerts are throttled to once per function per hour, with a maximum of 5 per day, to avoid noise.

Zero impact on production performance — scanning runs in WP-Cron background jobs. The runtime guard adds a single error handler registration at init. No database queries on the frontend unless a pre-flight is triggered.