Closed gudmdharalds closed 1 year ago
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: 1f4356b039b19371734451bda1c4fe6572559cf5)
This bot provides automated PHP linting and PHPCS scanning. For more information about the bot and available customizations, see our documentation.
Software versions
Options file (
|
PHP lint optionsPHP lint files enabled:
Lint modified files only:
Lint files with file extensions:
Directories not PHP linted:
SVG configurationSVG scanning enabled:
Scan added/modified files with file extensions:
Auto-approval configurationAuto-approvals enabled:
Non-functional changes auto-approved:
Files with file extensions to consider for non-functional change auto-approval:
Auto-approved file-types:
|
PHPCS configurationPHPCS scanning enabled:
PHPCS severity level:
Standard(s) used:
Runtime set:
Scan added/modified files with file extensions:
Custom sniffs included:
Custom sniffs excluded:
Directories not PHPCS scanned:
WPScan API configurationWPScan API scanning enabled:
WPScan API URL:
Directories scanned:
Directories not scanned:
Scan added/modified plugins based on headers present in files with file extensions:
Scan added/modified themes based on headers present in files with file extensions:
|
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