=== BreakGuard Upgrade Scanner ===
Contributors: coderevolution
Tags: compatibility, upgrade, php, scanner, wordpress update
Requires at least: 5.8
Tested up to: 7.0
Requires PHP: 7.4
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Detect upgrade risks before WordPress or PHP updates break your site.

== Description ==

**BreakGuard Upgrade Scanner** helps site owners and agencies catch upgrade problems *before* they hit production.

Unlike tools that only read WordPress.org metadata, BreakGuard Upgrade Scanner **scans your installed plugin and theme PHP files locally** for deprecated syntax, dangerous functions, suspicious obfuscation, and legacy database calls. It combines that with public listing data, update gaps, abandonment signals and readiness checklists for WordPress and PHP targets.

= Why use BreakGuard Upgrade Scanner? =

* **Local code scanner** — actionable warnings from files on your server (eval, shell_exec, base64_decode, mysql_query, and more).
* **Security heuristics** — clear messages like “Plugin X contains eval()”.
* **Maintenance badges** — Updated recently, Stale, Abandoned, Unknown source.
* **Missing update detector** — installed vs latest version with severity (Low/Medium/High).
* **Source classification** — WordPress.org, Premium/commercial, Custom/local, Unknown.
* **Chunked scanning** — scans 10 components per request with progress (“Scanning 34 / 97”) so admin stays responsive.
* **Weekly scheduled scans** — optional WP-Cron with email when new risks appear.
* **WordPress & PHP readiness** — checklist before upgrading core or PHP.
* **Site Compatibility Score** — simple 0–100 health score with breakdown.
* **HTML report export** — shareable compatibility report for clients and staging reviews.

= Important =

This plugin provides **heuristic guidance**, not a guarantee of runtime compatibility. Always test upgrades on staging. Premium and custom code may need vendor confirmation.

== Installation ==

1. Upload the plugin folder to `/wp-content/plugins/` or install from the WordPress.org plugin directory.
2. Activate through the **Plugins** screen.
3. Open **BreakGuard Upgrade Scanner** in the admin menu and click **Rescan**.

== Frequently Asked Questions ==

= Does this replace staging tests? =

No. Use BreakGuard Upgrade Scanner to prioritize what to test before you upgrade WordPress or PHP.

= Does it upload my code anywhere? =

No. File scanning runs locally on your server. WordPress.org API calls only fetch public metadata for known slugs.

= Will scanning slow down my site? =

Scans run in the admin (chunked) or via weekly cron. They do not run on front-end page loads.

== Screenshots ==

1. Dashboard with compatibility score, readiness panels, and component table.
2. Local code findings and security alerts per plugin.
3. Settings for target WordPress/PHP versions and weekly email alerts.

== Changelog ==

= 2.0.0 =
* Added local PHP file scanner for plugins and themes.
* Added security risk heuristics, maintenance badges, and source classification.
* Added chunked AJAX scanning with progress bar.
* Added weekly scheduled scans with email notifications.
* Added WordPress/PHP readiness checklists and site health score.
* Added HTML compatibility report export.

= 1.0.0 =
* Initial release with WordPress.org metadata audit.

== Upgrade Notice ==

= 2.0.0 =
Major update: local code scanning, chunked rescan, readiness checklists, health score, and HTML reports.
