docs: add SECURITY.md with a private reporting path - #413
Merged
Conversation
Closes #407. The reporter of #404 looked for a confidential channel before filing a network-exposure finding, found none — no SECURITY.md, private vulnerability reporting disabled — and filed publicly because the severity happened to be low. The next finding may not be. Points at GitHub's private advisory flow, which needs no infrastructure on either side, and states scope concretely rather than generically: the unauthenticated ZMQ embedding servers, the MCP stdio transport, the document readers that handle untrusted input by design, on-disk index metadata, and third-party credentials. Note: the advisory link only works once **Settings → Security → Private vulnerability reporting** is enabled. That toggle is a repository setting, not something a PR can change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
Closes #407.
@cmiic looked for a confidential channel before filing the network-exposure finding that became #404, found none — no
SECURITY.md, private vulnerability reporting disabled — and filed publicly because the severity happened to be low. The next report may not be.Adds a
SECURITY.mdpointing at GitHub's private advisory flow, which needs no infrastructure on either side.The scope section is deliberately specific rather than boilerplate, naming the boundaries where LEANN stops being local:
One thing this PR cannot do
The advisory link only works once Settings → Security → Private vulnerability reporting is enabled. That is a repository setting, not something a PR can change — issue #407's first suggestion. Worth flipping before or alongside merging this, or the link in the file leads nowhere.
🤖 Generated with Claude Code