The File Integrity page monitors your Joomla installation for files that have been modified since the last scan. It calculates a cryptographic hash for each file and compares it with the stored baseline, flagging any differences.
The action bar shows:
Three configuration chips beneath the action bar show:
If PHP memory_limit is 128 MB or less and no scan has been run, a low-memory warning badge is displayed.
Before the first scan, a prompt card invites you to run your first analysis.
After a scan completes, four metric cards appear:
| Card | Description |
|---|---|
| Files Scanned | Total files checked. A More Info link opens a modal with a pie chart of executable vs non-executable files and the slowest file details. |
| Modified Files | Files whose hash has changed since the baseline (shown in red when > 0) |
| Time Taken | Duration of the last scan |
| Extensions Updated/Installed | Number of extensions installed or updated since the last baseline. Click to open a modal listing them. |
A search field and a status filter (Compromised / OK / Exceptions) narrow the displayed results.
| Column | Description |
|---|---|
| Name | Filename (files only; directories show no name) |
| Path | Full server path |
| Size | File size in human-readable format; "Not calculated" for inaccessible files |
| Status | Badge: green (OK), yellow (Exception), red (Compromised) with the descriptive note |
| Last Modified | File modification timestamp; wrapped in a red badge for compromised files |
When the Compromised filter is active and items are selected:
When the Exceptions filter is active and items are selected:
A file flagged as compromised has a hash that does not match the stored baseline. This can mean the file was legitimately updated (e.g. during a Joomla or extension update) or that it was tampered with. Review all flagged files carefully before adding them as exceptions.
When more than 3,000 files are flagged, a warning is displayed suggesting that you verify the scan path and exception list configuration.

