Browser Demo — the project's own Python engine, running locally in your browser
Local processing only. Your backup ZIP is read inside your own browser using WebAssembly
(Pyodide). No backup, PHP source, file path, or scan result is ever uploaded to a server. The only network
requests this page makes are to download the public Pyodide and JSZip libraries, and later to fetch
official WordPress.org core checksums (a version number only, never your files).
Backup ZIP
or drag and drop
No file selected
A WordPress site or backup archive. Nothing is extracted until the archive passes the safety checks.
Safety Limits
Maximum upload size25 MB
Maximum uncompressed size50 MB
Maximum archive entries2,000
Maximum files scanned1,000
Maximum size per file5 MB
Maximum compression ratio100:1
An archive that exceeds any limit is rejected before a single entry is extracted.
Archive inspection, backup scanning, downloadable JSON/HTML reports, and snapshot comparison are
available. Partial WordPress core integrity verification is available in this demo: it compares the
files listed in the official WordPress.org checksum set against the extracted archive. It does not
cover plugins, themes, uploads, or any other file outside that set.
Archive Inspection
The archive was inspected by the upstream inspect_zip()
implementation running locally. No entry was extracted and no file content was read.
Summary
Entries
Entry
Size
Compressed
Safe
Symlink
Traversal
Duplicate
Status
Backup Scan
Findings come from the upstream indicators.scan_directory() implementation. PHP files are read
as plain text and are never executed. Every finding is an indicator with status
suspicious — none of them is confirmed malware.
Summary
Findings
Severity
Confidence
Category
Indicator
File
Line
Evidence
Download Report
Reports are generated in your browser and saved straight to your device. The HTML report is a download
only — it is never opened automatically and never inserted into this page. Evidence from sensitive
files (wp-config.php, .env, *.pem, *.key, id_rsa, names containing "credentials", and *.sql) is
always redacted.
Core Integrity Verification Partial — browser based
The archive is extracted into a temporary in-memory directory, the official checksums for the
detected WordPress version and locale are fetched by your browser from
api.wordpress.org, and the extracted files are compared with the upstream
core_verify.verify_core() implementation. Only the version, the locale, and the
official checksum list ever leave your browser — no file, path, or hash is sent anywhere.
Partial verification. Only files that appear in the official WordPress.org
checksum set are compared. Plugins, themes, uploads, wp-content, and any other file
outside that set are not checked. A result without mismatches is therefore not a proof that the
installation is free of injected code.
Summary
Files that did not match
File
Status
Expected SHA-256
Actual SHA-256
Snapshot Comparison
Compare two backup archives to see which files were added, removed, modified, or left unchanged.
Both archives pass exactly the same safety checks as the single-archive scan, and nothing is extracted
unless both of them are accepted.
Snapshot A — older backup
or drag and drop
No file selected
Snapshot B — newer backup
or drag and drop
No file selected
Files are matched by relative path and SHA-256 hash. File contents are never shown and uploaded PHP
files are never executed.
Snapshot Comparison Result
Produced by the upstream compare.compare_snapshots() implementation running locally.
Snapshot A is the older backup and Snapshot B the newer one, so a file that only exists in Snapshot B
is reported as added and a file that only exists in Snapshot A is reported as removed.
Summary
Files
Status
Path
Snapshot A SHA-256
Snapshot B SHA-256
Download Result
The JSON file is produced in your browser by the upstream report generator and saved straight to your
device. It contains file paths and hashes only, never file contents.
⚠️ Browser-Specific Limitations
Runs entirely in your browser via Pyodide; no files are uploaded to any server.
The first load downloads the Pyodide runtime (tens of megabytes) and may take around 30 seconds.
Large archives can exceed browser memory limits; use the command-line tool for very large backups.
Only ZIP archives you explicitly select can be analysed — the demo cannot read a local directory.
Snapshot comparison needs two ZIP archives; both are read into the in-memory filesystem, compared by path and SHA-256 hash, and deleted afterwards.
Files that could not be hashed in one of the two snapshots are reported as limitations instead of being classified as added or removed.
Symlink detection is stricter than upstream: the upstream is_symlink() helper matches only the exact mode 0o120000, so this demo also applies the standard S_IFLNK type-bit mask and rejects symlinks that carry ordinary permission bits.
Findings are indicators that require manual review. A clean scan does not prove a site is free of malware.
Core integrity verification is partial and browser based. It compares only the files listed in the official WordPress.org checksum set for the detected version and locale; every other file in the archive is ignored, and a version that WordPress.org does not publish checksums for cannot be verified at all.
Core verification needs network access to api.wordpress.org. The request sends the version and locale only, never file names, hashes, or file contents, and the comparison itself runs locally.