Attic — Safe Database Cleanup (Undo-Friendly)
| 开发者 | rainynewt |
|---|---|
| 更新时间 | 2026年9月11日 00:39 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv3 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Tables you quarantine are renamed, not dropped — restorable by default for 30 days (configurable)
- Every option is backed up before removal
- Nothing is called orphaned with confidence until Attic has confirmed the owning plugin's actual files are gone from disk and searched your code for references — weak evidence stays at "review" rather than becoming a recommendation What Attic finds:
- Autoloaded option bloat — oversized options that load on every page request, ranked by size against Site Health's 800 KB line.
- Ghost cron events — scheduled hooks with no registered callback, firing forever and doing nothing.
- Orphaned tables — tables no installed plugin claims, with reclaimable megabytes up front.
- Stranded transients — expired timeout pairs and orphaned rows.
- Leftovers from deleted plugins — data whose owning plugin is absent from disk entirely.
- Orphaned meta — post meta, comment meta, user meta, and term meta whose parent row no longer exists.
- Quarantine, never delete. Options are stored before removal. Tables are renamed (
wp_attic_quarantined_*), never dropped until a purge window passes. - Nothing is called orphaned until your code has been searched for it. Attic reads through your plugins, mu-plugins and themes, plus
wp-config.php, looking for every candidate name before promoting anything to high confidence. (PHP, JS, JSON and.incfiles;node_modules,vendor,distandbuilddirectories are skipped.)
- Site owners who've installed/removed a lot of plugins over the years
- Agencies maintaining client sites and doing housekeeping
- Anyone whose Site Health page flags "autoloaded options" and doesn't know what to do about it
wp_attic_quarantined_*) and options are backed up first, with one-click restore inside the purge window (default 30 days, configurable). Permanent removal only happens once a quarantined batch passes the purge window un-restored, or if you purge it yourself on purpose. Attic also checks plugin files on disk and searches your code for references before promoting findings to high confidence, so uncertain items stay at "review."
WP-CLI
Run scans from the command line for automation and CI/CD pipelines:
wp attic scan— run a full database auditwp attic findings— list and filter findingswp attic quarantine— manage quarantine batcheswp attic status— check plugin statuswp attic map status— inspect the bundled attribution map
- Daily, weekly, or monthly scan frequency
- Email summary with findings count, new vs resolved findings, and total autoloaded size
- Comparison between scans to detect regressions
- Autoload size trend over the last 10 scans
- 800 KB Site Health limit indicator
- Trend direction (increasing, decreasing, stable)
- Export chart as PNG or table as CSV
- Aggregated findings across the network
- Per-site scan status and autoload metrics
- Network-wide scan capability
- Proper handling of network-active plugins
wp attic map status— show the bundled map version and entry count- Add your own attributions with the
attic_prefix_map_entriesfilter
assets/vendor/chart.umd.min.js, used
only to draw the autoload trend chart in the admin. It is served from your own
site. Attic makes no outbound network requests of any kind.
安装:
- Install and activate.
- Go to Tools → Attic.
- Click Scan.
- Review evidence for each finding (confidence, size, code references).
- Quarantine what you want gone — recoverable for 30 days by default (configurable) if you change your mind.
常见问题:
Is this safe?
The scan is read-only. Nothing changes until you take an explicit, confirmed action. Core options like siteurl, active_plugins and cron can never be flagged, and neither can anything on your own protected list or the attic_protected_options filter.
How do I undo something?
Tools → Attic → Quarantine. Every action creates a batch; restore a whole batch in one click. Batches auto-purge after 30 days (configurable).
Why does my finding say "review" instead of "high"?
For most rules, high confidence requires the owning plugin to be absent from disk (or the option to be size-flagged and unread), and zero literal and zero prefix references anywhere in your code. Dynamic option names never literal-match, so even a weak signal keeps a finding at "review". If your filesystem could not be read, everything is marked unverified rather than guessed at. Two rules are exceptions, because a code search cannot tell you anything useful about them: an expired transient and a meta row whose parent is gone are facts about your database, not guesses about your code. Those are reported as high confidence on their own evidence.
Does it work with external object caches?
Yes — when Redis/Memcached is active, transients never touch the options table, and Attic says so instead of showing a meaningless clean bill of health.
Multisite?
Yes. Single-site, subdirectory multisite, and subdomain multisite installs all work. Network-wide fleet scanning is available via the network admin dashboard.
Which plugins does Attic work with?
Attic works with all WordPress plugins — it's a read-only cleanup tool that doesn't touch plugin data unless you explicitly quarantine it. The attribution map helps identify which plugin owns which database entries, but the scan works regardless of whether a plugin is in the map.
Plugins with known prefixes in the attribution map get named attribution, and the "leftovers from a deleted plugin" rule relies on the map to know which prefixes belonged to which plugin.
Data belonging to a plugin that is not in the map is still found by the other rules — an oversized autoloaded option, an orphaned table or a dead cron event is detected either way. It just shows its owner as "unknown". You can add your own entries with the attic_prefix_map_entries filter.
Does Attic delete plugin data?
No. Attic quarantines data (renames tables, copies options), never deletes. You can restore anything from Quarantine within the purge window (default 30 days, configurable).
What about multisite network-active plugins?
Attic correctly detects network-active plugins and never flags their data as orphaned, even if they're deactivated on individual sites.
更新日志:
- New: Orphaned meta detection (post, comment, user, term meta with a missing parent row).
- New: Scheduled scans with an email digest, WP-CLI support, and a network dashboard for multisite.
- New: Autoload trend chart, exportable as PNG or CSV.
- Fix: Several rules were skipping findings they should have caught (stranded transients, three of four meta tables). Re-scanning is recommended.
- Fix: Orphaned-table detection no longer flags other sites on shared multisite/database setups.
- Improved: No more per-page-load database writes; scans and quarantine are unaffected.
- Improved: No CDN or outbound requests — everything ships with the plugin.
- Fix: Quarantine action now correctly updates finding state (broken by SQL syntax error).
- Fix: Orphan tables rule no longer flags Attic's own tables on sites with nested table prefixes (e.g. wp_pc_attic_*).
- Add: Stop scan button to abort long-running scans mid-flight.
- Fix: Findings page defaults to latest completed scan instead of showing duplicates across all scans.
- Fix: Scan complete state now hides progress bar and stop button cleanly.
- Fix: Empty quarantine batches are cleaned up automatically.
- Initial plugin release: read-only database audit with quarantine-based undo, five detection rules, budgeted scan engine, reference scanning, quarantine with batch restore, and attribution map.