Linux 软件免费装

Upaccn PHP Upgrade Risk Audit

开发者
更新时间 2026年10月4日 15:43
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

php developer tools site health php compatibility php upgrade

下载

0.1.0

详情介绍:

Upaccn PHP Upgrade Risk Audit helps you answer one practical question before changing PHP on a WordPress site: which installed plugin or theme could block this upgrade? Choose a target PHP version, select the components you want to inspect, and run a local static-analysis scan. Results are grouped by plugin or theme and summarized as Ready, Review, or Blocked, with the relevant file, line, compatibility rule, and finding available for technical review. Highlights Important limitation Static analysis can identify known PHP compatibility patterns, but it cannot execute every runtime path and cannot guarantee that a site will work perfectly after an upgrade. Always validate the final PHP change on staging before changing production. Privacy Scanning and scan state stay on the WordPress installation. Upaccn PHP Upgrade Risk Audit does not upload plugin or theme source code and does not include telemetry in this version.

安装:

  1. Upload the plugin or install it from WordPress.org when available.
  2. Activate Upaccn PHP Upgrade Risk Audit from the Plugins screen.
  3. Go to Tools → Upaccn PHP Upgrade Risk Audit.
  4. Choose the PHP version you plan to upgrade to.
  5. Select the plugins/themes to inspect and click Scan selected components.

常见问题:

Does this change my PHP version?

No. It only analyzes source code. Changing the server PHP version remains a hosting/server operation.

Does the scanner modify plugins or themes?

No. Scans are read-only.

Does it work when shell functions are disabled?

Yes. The release package includes the scanner runtime and runs it in-process. It does not require shell execution.

Can it scan premium or custom plugins?

Yes, as long as the code is installed on the WordPress site and readable by WordPress. The scan does not depend on a public compatibility database.

Why is Upaccn PHP Upgrade Risk Audit itself not in the component list?

The scanner deliberately excludes itself. Its bundled PHP_CodeSniffer/PHPCompatibility engine is an analysis dependency and can generate self-referential findings that do not help you assess the rest of the site.

Does a Ready result guarantee the PHP upgrade is safe?

No. A Ready result means the static scanner did not find a known blocking pattern in the selected source. You should still test the actual upgrade on staging.

更新日志:

0.1.0