WP Hide writes its configuration into wp_options under the wph_ prefix: rewrite slugs for wp-admin, wp-login, wp-content, wp-includes, plus blocked default-path rules and asset rewrites. The admin UI is a long tabbed form, which is fine for setup but slow when an audit asks which overrides are actually active.

SleekView reads wp_options directly and exposes wph_ keys as a chartable dataset. Each row becomes a configurable record with the option name, current value, autoload flag, and last-modified timestamp pulled from related history if present.

Charts then count, group, and trend those rows: active rewrites by category, distribution of blocked default paths, count of changes per week. The same dataset feeds Table and Kanban views, so the security team can pivot from a chart card to the underlying record without rebuilding the query.

WP Hide is effective when the configured rewrites actually match the intended posture. Without a dashboard, that match is hard to verify, every audit means clicking through tabs and writing the active values into a spreadsheet. SleekView Charts reads the same wp_options rows the plugin already maintains and renders them as KPI tiles, category splits, and change trends.

The plugin keeps owning the rewrites, SleekView just surfaces what is enabled and what changed. Saved views travel with the site, so the next maintainer inherits the audit view rather than rebuilding it from scratch. Charts can be exported as CSV for compliance evidence when an external review asks for it.