Skip to content

SECURITY: clarify status of parse errors #58

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.

Sign up for GitHub

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

Open
jrfnl wants to merge 1 commit into
base: main
Choose a base branch
from
Open

SECURITY: clarify status of parse errors #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,9 @@ Running PHP_CodeSniffer against an untrusted or attacker-modifiable checkout mus

CI environments processing untrusted contributions are responsible for appropriate isolation, including restricting access to credentials, secrets, privileged services, and sensitive network resources.

PHP_CodeSniffer is intended to scan valid PHP code. It is the responsibility of projects using PHP_CodeSniffer to validate code against parse errors before scanning such code with PHP_CodeSniffer.
Attack vectors which can only be triggered by an attacker introducing deliberate parse errors in otherwise valid code, do not classify as security vulnerabilities. They do qualify for security hardening and reports are appreciated.

## Supported Versions

For all repositories in the PHPCSStandards organisation, the latest patch version of the current major is supported for security updates.
Expand Down
Loading