-
Notifications
You must be signed in to change notification settings - Fork 22
WPScan fixes: Ensure that WPScan type of items are not removed from results when filtering #339
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
Conversation
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.
Changes look ok, not sure why tests are failing
Thanks @chriszarate ! The integration tests fail due to GitHub HTTP request rate limit. This is not easy to fix, but is on the agenda to resolve. I will run the tests manually. |
No issues were found to report when scanning latest commit (commit-ID: 1f4356b) This bot provides automated PHP linting and PHPCS scanning. For more information about the bot and available customizations, see our documentation. Scan run detail
|
This pull request will ensure that WPScan type of items are not filtered from results due to the underlying files being auto-approved.
The rationale is that WPScan type of items should always be reported; the fact that a add-on has a known issue or is obsolete will not be overridden by the file-ending or the fact that the changes were non-functional.
TODO:
Scan run detail
report as applicablepull request with obsolete or vulnerable plugin or theme is not auto-approved
.database of previously reviewed, safe code
.PHPDoc
comments are up to date for functions added or altered