Official comparison
Compare eligible core, plugin and theme files with trusted WordPress.org packages.
Trusted-source comparison
Know what changed—and whether it belongs.
Nexus compares WordPress core and eligible plugin or theme packages against trusted sources, identifies unexpected changes and supports controlled repair without guessing.
Core checksumsRepository comparisonChanged-file reviewControlled repair
INTEGRITY ENGINEBASELINE VERIFIED
WordPress coreChecksums match
Plugin fileUnexpected modification
Custom componentNo public source; review required
Change awareness
Prioritize unexpected, added or modified files for deeper scanning and review.
Controlled repair
Restore known official files only after evidence and recovery safeguards are available.
Trust is evidence
A clean version label does not prove clean running files.
Files can be altered after installation while the plugin version remains unchanged. Integrity comparison reveals the difference between the expected package and the code actually present.
- WordPress core checksum and source comparison
- Plugin and theme repository comparison where eligible
- Unexpected file, modification and omission reporting
- Repair workflows that preserve evidence and restore points
Capability map
From package trust to file-level evidence.
Integrity provides the structural evidence that version-only vulnerability monitoring cannot.
Core integrity
Compare WordPress core files with official checksums and package sources.
- Modified core files
- Unexpected files
- Controlled core repair
Plugin and theme comparison
Download or use trusted official packages for eligible component comparison.
- Added and changed files
- Missing package files
- Source provenance
Changed-file prioritization
Feed unexpected changes into the scanner before spending time on an entire large filesystem.
- Faster first review
- Evidence snippets
- Full scan remains available
Repair and rollback
Replace eligible official files while preserving evidence and a path back.
- Restore points
- Quarantine before replacement
- Post-repair verification
Operational flow
Compare the running site with a trusted source.
The verdict depends on whether a suitable source exists and whether local customization is expected.
Identify
Nexus inventories the core or component and its expected source.
Compare
File paths, hashes and package structure are evaluated.
Review
Unexpected differences receive context and scanner evidence.
Repair
Eligible files are restored deliberately, followed by verification.
Use source provenance before repair.
- Preserve evidence for modified files
- Distinguish expected customization from unknown change
- Use official packages only when identity matches
- Verify after repair
Overwrite custom software blindly.
- Repair premium code from a free namesake
- Assume all modifications are malware
- Delete unexpected files without review
- Present version matching as file integrity
Feature questions
What buyers usually want to know.
Is integrity scanning the same as malware scanning?
No. Integrity asks whether files match a trusted source. Malware scanning asks whether content or behavior appears malicious. The strongest investigation uses both.
Can Nexus repair WordPress core?
Controlled core repair is available where an official source is clear, with evidence and recovery safeguards.
What about locally customized themes?
Expected local changes should be documented or compared with a trusted local baseline. Nexus should not overwrite them blindly.
Does a clean integrity result guarantee the site is not compromised?
No. Database persistence, stolen credentials, malicious configuration and custom code can exist even when official packages match. Integrity is one defensive layer.
Lumiverse Nexus PRO
Make software integrity visible before it becomes an incident.
WordPress integrity and repository comparison tools are included in Nexus PRO.