Repository navigation
docs: Add SECURITY.md - #18
Merged
Merged
Conversation
mkaruza
approved these changes
Oct 28, 2026
utkarash2991
approved these changes
Oct 28, 2026
utkarash2991
force-pushed
the
add_security_md
branch
from
October 28, 2026 07:43
12e187a to
82e9306
Compare
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
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.
What kind of change does this PR introduce?
Adds a SECURITY.md file so we can get better signal on our security reports.
What is the current behavior?
Agents and researchers send us reports that are invalid or out of scope.
What is the new behavior?
Agents read the SECURITY.md and send us better security reports.
Additional context
Linear Issue