Repository navigation
docs: add a SECURITY.md disclosure policy - #727
Merged
Merged
Conversation
26 tasks done
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.
Context
The repository has no
SECURITY.md(low-severity audit finding C26). One is bundled into the large AI-native SDLC PR #635, but that is a 33-file policy change; this adds just the disclosure policy so the finding is resolved without waiting on the bundle.Changes
SECURITY.md: private GitHub Security Advisory flow (+ security@backblaze.com fallback), supported-versions, response-time targets, and scope. Content adapted from chore: adopt the AI-native SDLC playbook and repository policies #635 with itsRELEASE.mdcross-reference removed so it stands alone.Verification
Refs #711