Data Storage and Uninstall

What the plugin stores#

Where	What
Table {prefix}_ers_findings	One row per finding: scan ID, plugin/theme key and version, rule ID and status, severity, confidence, file, line, snippet and evidence.
Option ers_scans	Scan history (last 10): ID, status, start and end time, WordPress version, the plugins and themes scanned, and stats.
Option ers_runtime_{scan_id}	The runtime inventory (meta boxes and editor assets) of each kept scan.
Option ers_last_simulation	The last successful editor simulation, kept so later scans and WP-CLI can fall back to it.
Options ers_observed_meta_boxes, ers_observed_editor_assets	Meta boxes and editor assets recorded when an administrator opens the real block editor.
Options ers_scan_state, ers_scan_prep, ers_simulation_error	The cursor of the scan in progress; removed when it ends.
Option ers_white_label	The white-label setting.
Option ers_db_version	Schema version.
StoreEngine SDK options	License key, status, expiry and the daily license check event.

No absolute server paths are kept in the scan history; files are stored relative to the plugins or themes folder.

Uninstall#

Deleting the plugin from Plugins drops the table, deletes every option above (including per-scan runtime inventories) and clears any queued ers_process_scan_chunk action. On multisite it does this for every site.