Clarify security classification for unsanitized args#30
Merged
Conversation
Clearly, some functions _should_ be hardened against malicious arguments. Clarify this only applies to some functions.
TimWolla
approved these changes
May 2, 2026
Member
TimWolla
left a comment
TimWolla
left a comment
There was a problem hiding this comment.
This is an improvement. Perhaps it also makes sense to give an example for the other way around where an input would clearly be a security issue if mishandled, e.g. escapeshellarg().
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Clearly, some functions should be hardened against malicious arguments. Clarify this only applies to some functions.