Essential Plugin for Developers
By polyxgo (sanddesert88) on February 25, 2025
This plugin is extremely helpful for developers and is indispensable for reviewing and refining code before release. Thank you to the WordPress team for developing such a truly useful plugin.
I have a suggestion regarding the code inspection feature—it would be beneficial to integrate function call analysis. For example, when source code calls intermediary functions that handle nonce verification, sanitization, and other input validations within shared classes, it may result in false positives. This could potentially impact the efficiency of the plugin review process.
Overall, this plugin is fantastic for me! Many thanks to the WordPress Team!
Warm regards,
This plugin is a real blessing!
By Anne-Mieke Bovelett (annebovelett) on January 19, 2025
I'm working on a Block plugin, for the first time in my life, with the intention to share it in the repo. As I'm walking uncharted territory, The PCP is a real blessing! Thank you, dear Review Team, for creating this.
Very useful , Thanks !!
By Njengah on January 4, 2025
This plugin is excellent for catching common mistakes before submission. It significantly saves time by reducing the back-and-forth process. I used it for the first time, and I really liked how efficiently it worked.
best tool for WordPress plugin developers
By Samsul Islam Rana (ranafge) on December 12, 2024
The best tool for WordPress plugin developers
By Carlos Longarela (carloslongarela) on December 7, 2024
This tool is a must for every WordPress plugin developer. You can use phpcs with WordPress standards and other useful tools, but this is an essential step to check your plugin, not only if your intention is to publish to WordPress public repo. Accomplish these standards is a must for everyone who works as plugin developer.
Thanks, plugin team, for this powerful tool. Now our developer lives are easier.
Tons of false positives
By Bob (prasunsen) on November 15, 2024
Run it on any plugin, including popular ones like Woo and you'll see tons of nonsense "Error" messages about inescaped output. This doesn't help anyone. These so-called error messages appear even for static text or well trusted data.
Just a random example from Woo:
The plugin reports "WordPress.Security.EscapeOutput.ExceptionNotEscaped" for this:
throw new Exception( sprintf( __( 'Could not find classname for order ID %d', 'woocommerce' ), $order_id ) );
$order_id is already int, ensured by the function, and additionally %d ensures it cannot output anything dangerous.
You have to either make this smart enough to find real issues or remove these nonsense messages entirely.
How is this helping anyone?
How To Add Custom Rules To xml File?
By Aditta Amin (adittaamin) on November 6, 2024
Need To Add Custom Rules Into This Plugin That Will Check The Naming Conventions and Global Prefixes.
There is no reason to use this plugin.
By strongDev (etopizdets) on October 25, 2024
István Márton probably has a high opinion of himself. But this is my user experience, which I’m sharing. I’m wondering, how did we live without this plugin before?
Gives more information than I expected
By Debesyla on October 5, 2024
It's great!
This is awesome! WP-CLI supported!!!
By Angelo Mandato (amandato) on October 3, 2024
I am very impressed with this plugin. I am in the final steps of submitting a new plugin and through the approval process this has helped speed up the process.
I am developing a script that will install this plugin if not already installed then run the cli tool to create a report. Eventually this will be a step in the CI/CD pipeline.
cli usage can be found on the project's GitHub project under docs/CLI.md
I got some ideas for this plugin to make it more friendly for GitHub, starting that convo with the contributors next.