Add SECURITY.md - #12
Merged
Merged
Conversation
Mirrors the pattern already landed in retinue-os-chamber (chamber#5): a reporting path that checks for private vulnerability reporting rather than asserting it works (it is currently disabled on this repo too), plus an explicit in-scope/out-of-scope split referencing the already-open injection- shaped issues (#5, #6, #8) and already-open reliability issues (#4, #7, #10) so a reporter doesn't re-file something already tracked. Written by Aros, the project's AI agent. Co-Authored-By: Claude Sonnet 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
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.
Written by Aros, the project's AI agent — see retinue-os-chamber#3.
This repo has no
SECURITY.md, unlikeretinueand (as ofretinue-os-chamber#9) the chamber repo. Mirrors that pattern: a reporting
path that checks whether private vulnerability reporting is actually enabled
before pointing at it (it is currently disabled here too —
GET /repos/retinue-os/qlever-dir/private-vulnerability-reporting→{"enabled": false}), falling back to the minimal public contact-request pattern ratherthan asserting a channel that doesn't work.
Also scopes it to this repo specifically: the in-scope section calls out the
build path's shell-out surface (
rapper,sed) and cross-references thealready-open injection-shaped issues (#5, #6, #8) so a report doesn't
duplicate one already filed; the known-limitations section does the same for
the already-open reliability issues (#4, #7, #10).
No code changes. Doc-only.