AntiVirus is the long-running theme-file scanner by pluginkollektiv. It does not create custom tables: schedules, the recipient address, last-scan timestamps, and the per-file safe list live in wp_options under keys like antivirus_safe_browsing, antivirus_cronjob, and antivirus_white_list. The settings page surfaces a summary plus the last scan, but the historical list of suspicious matches, the rule that flagged each file, and the whitelist edits over time are hidden inside serialized payloads.

SleekView reads those option values and unpacks them into rows: one per finding, with the file path, the matched pattern, the scan timestamp, and the whitelist status as first-class columns. Joins to the active theme table promote the parent theme and the relative path so the same view works across multisite installs running different themes. Saved views capture filters and columns so weekly scans stop being a one-off email check.

Writes route through the plugin's own update path. Adding or removing a file from the safe list updates antivirus_white_list in the structure AntiVirus expects, and the next scheduled scan reads the new state without a mismatch. Annotations and reviewer notes are stored separately so the original AntiVirus payload stays untouched.

Theme-file scanning is one of those tasks that sounds simple until a single flagged file shows up across a hundred client sites and nobody can remember whether the last reviewer signed off on it. AntiVirus has done that job reliably for years, but it was designed to keep its footprint tiny by storing everything in wp_options. That choice is great for performance and for compatibility with hosting backups, but it means the actual list of findings, the reviewer notes, and the history of safe-list edits are hidden inside serialized arrays.

SleekView turns those arrays into a grid so a reviewer can see every flagged file across every scanned theme as a row with proper columns. Saved views capture the questions a security team asks repeatedly, like which patterns fire on the active theme each week, and inline edits route through the plugin's own update path so the whitelist payload stays valid for the next scan. The annotation layer is stored separately, which keeps AntiVirus's configuration record clean while still giving reviewers a place to document the why behind a whitelist decision.

The result is a faster, more accountable review loop without forcing the plugin to grow new tables.