doc: clarify security triage dispositions and permission boundaries - #65436
Open
RafaelGSS wants to merge 1 commit into
Open
doc: clarify security triage dispositions and permission boundaries#65436RafaelGSS wants to merge 1 commit into
RafaelGSS wants to merge 1 commit into
Conversation
Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
Collaborator
|
Review requested:
|
jasnell
approved these changes
Aug 20, 2026
Trott
approved these changes
Aug 20, 2026
RafaelGSS
added
the
author ready
legendecas
approved these changes
Aug 20, 2026
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
5 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.
Clarify
SECURITY.mdby defining security triage dispositions, documenting same-process self-harm exclusions, and separating Permission Model reports into vulnerability, security-interest, and excluded cases. Also correct theworker_threadsguidance: workers with modifiedexecArgvorenvmay not inherit the parent permission configuration, while worker creation itself remains gated by--allow-worker.