FileOps Monitor helps administrators understand what changed in their WordPress installation. Create a baseline from a known-good site, run a manual scan, and review file differences and today’s observed changes.

Part of Operations Suite. All functionality in this plugin is free and available without registration, a license key, a subscription or a trial period.

Features

SHA-256 baseline in dedicated database tables.
Added, modified, deleted and restored file detection.
Content comparison even when modification time and size have not changed.
Core, plugin, theme, upload, must-use plugin, drop-in and root classification.
File counts, paginated differences, hashes, timestamps and today’s observation events.
Review priorities for sensitive files and executable PHP files in uploads.
Path, filename, extension and component exclusions.
Short scan batches with resume and cancellation.
Previous completed report retained after interruption or failure.
Baseline replacement only after explicit administrator confirmation.

Usage

Open FileOps Monitor > Exclusions and review the scope.
Open the Dashboard and choose Run first scan.
After a legitimate file change, choose Run scan.
Review Changed files and Today’s file changes.
Only replace the baseline after accepting the current files.

Scope and limitations

This is a manual change monitor, not a real-time service, backup, repair tool or guaranteed malware scanner. A baseline is an observed reference, not proof that files are safe. Change causes are unknown; review priorities do not establish malicious intent.

Eligible types include PHP, JavaScript, CSS, HTML, JSON, XML and selected configuration files. Binary/media content is not monitored. Files outside the WordPress root, symbolic links, unreadable paths, files above 16 MB and directories deeper than 40 levels are unsupported. Encountering an unsafe or unreadable monitored path stops the scan instead of publishing partial deletion results. Exclusions deliberately remove paths from coverage.

The filesystem can change during a scan. Common directory changes are detected and require a restart, but a scan is not a transactional filesystem snapshot. Avoid concurrent deployments, imports and updates when possible.

Single-site installations are supported. Content directories must be inside the WordPress root. Very large individual directories and slow filesystems may require a narrower scope. Database named locks and transactional tables are required. Official core checksum verification, update attribution, scheduling, email alerts and code diffs are not part of this release.

Privacy

All processing is local. FileOps Monitor makes no external requests and sends no files, hashes, paths, user information or telemetry to outside services.

Relative paths, SHA-256 hashes, sizes, modification times, component labels and events are stored in the database. Scan records include the initiating administrator’s user ID. No file contents or source revisions are stored, including for wp-config.php. Scan actions require administrator capability and a valid nonce.

Deactivation retains data. Uninstall also retains data by default. Enable uninstall cleanup to remove only FileOps Monitor tables and settings when deleting the plugin.