-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CMS-859] Add theme vulnerability check #103
[CMS-859] Add theme vulnerability check #103
Conversation
When this command runs on the platform, it does not explicitly utilize the --all flag, but that’s because the plugin command (which does have an option for --all) does not actually implement this logic - it will pull all plugins and makes no distinction whether they’re active or not. This commit will just assume that when anyone (including the platform) runs the “all” command, it will expect the --all flag is enabled.
Thanks @kyletaylored ! @greg-1-anderson Up for building this into the Phar when you have a moment? |
When this command runs on the platform, it does not explicitly utilize the --all flag, but that’s because the plugin command (which does have an option for --all) does not actually implement this logic - it will pull all plugins and makes no distinction whether they’re active or not. This commit will just assume that when anyone (including the platform) runs the “all” command, it will expect the --all flag is enabled.
…heck into add-theme-check # Conflicts: # .travis.yml
93e8b52
to
c940821
Compare
Build reports:
|
@danielbachhuber I had committed a lot here, some of it to try and get successful tests to run on TravisCI, so I went ahead and started a TravisCI to Github Actions migration (#107) which should probably get merged first, then we can start adding in these updates. What do you think @greg-1-anderson? |
Yeah, looks good to me. Let's rebase this against #107 after that PR is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM. I've tested locally using wp --require=wp-cli/wp_launch_check/vendor/autoload.php launchcheck themes
and it works as expected. Looks like it's been updated with the main branch, as well, so this should be g2g.
Even though we use WPScan (formerly WPVulnDB), we only made use of the plugin vulnerabilities and never the theme vulnerabilities. This PR adds in a new command for checking the themes, similar to how
wp launchcheck plugins
works.There are also a few typos and grammar pieces that were fixed as well.