Rating: 3 stars
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?
Rating: 2 stars
Need To Add Custom Rules Into This Plugin That Will Check The Naming Conventions and Global Prefixes.
]]>Rating: 1 star
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?
]]>Rating: 5 stars
It’s great!
]]>Rating: 5 stars
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.
]]>Rating: 5 stars
Thanks, it is useful to find security issues like missed escape function or sanitization even if you do not plan on submitting the plugin to www.remarpro.com.
]]>Rating: 5 stars
This tests for a ton of different aspects of plugins. A must have for developers
]]>Rating: 5 stars
DevTools for WordPress is an essential toolkit for WordPress plugin developers, providing a comprehensive suite of features to simplify and accelerate the development process. This plugin is designed to enhance your coding efficiency, improve testing workflows, and ensure seamless integration of your custom plugins into WordPress environments.
]]>Rating: 5 stars
We always use this plugin before submit to WordPress plugin repository
]]>Rating: 5 stars
A great way to validate plugins against WordPress ecosystem standards. Yet another useful tool.
]]>Rating: 5 stars
This tool is very useful, not just for developers.
Since finding it, I use it to test any new plugins I want to use.
I have had good responses from plugin author’s when contacting them to resolve matters.
Rating: 5 stars
I like it
]]>Rating: 5 stars
Wonderful plugin.
Looking forward to more features.
Rating: 3 stars
Very helpful.
Nevertheless I would have expected that you have run the check on your own plugin and fixed all errors.
Errors should be automatically priorized by severity in future versions, e.g.: blocker, critical, major, minor, trivial.
]]>Rating: 5 stars
Awesome plugin to learn and improve code and myself. Thank you!
]]>Rating: 2 stars
Unfortunately, one of the most dangerous PHP functions shell_exec is required and this is not specified anywhere from what I can see.
]]>Rating: 5 stars
Great tool. It will probably save a lot of time for those who are waiting for their plugins to be reviewed, and would probably get a lot of homework to do.
Great initiative. Well done!
Hopefully it will make new plugins to get an approval faster. ??
]]>Rating: 5 stars
That a great tool! Thank you guys. It can help us quickly identify some issues with our code that might otherwise be overlooked.
I hope it gets better by the time and save time to a lot of people ??
]]>Rating: 5 stars
I found a problem in the plugin and created a new issue in the repo. They fixed it and released a new version in less than 24hs! Very responsive team ??
]]>Rating: 5 stars
As a Plugin Developer I want to get feedback as soon as possible, and this pluging give feedback about some basics things as
“PHP Code Sniffer is not available. Try running?composer install?first.”
I will work more with this tool and get back with more details!
]]>