wp-plugin-review

Run a comprehensive WordPress plugin review by passing the target plugin directory to the review tool, which executes PHPCS, PHPStan, and PHPUnit, then performs a manual check against repository guidelines to output a detailed Markdown report.

An automated WordPress plugin security and coding standards check covers security vulnerabilities, WordPress Coding Standards compliance via PHPCS, static analysis with PHPStan, and unit-test coverage through PHPUnit, producing a report with severity levels and fixes.

Yes, you need PHP tooling installed to check WordPress plugin repository readiness, specifically PHPCS with WordPress Coding Standards, PHPStan, and PHPUnit, which the review process relies on to surface defects and compliance issues.

Yes, you can use PHPStan and PHPUnit together for WordPress plugin code analysis; the review process integrates both tools, using PHPStan for static analysis and PHPUnit to verify unit-test coverage alongside PHPCS checks.

The best way to fix security vulnerabilities found during a WordPress plugin review is to consult the generated Markdown report, which provides concrete remediation steps and severity levels for each identified issue.

Your WordPress plugin review may fail accessibility considerations if the manual code review identifies non-compliance with WordPress.org repository guidelines, security best practices, or accessibility standards, all detailed in the output Markdown report.