Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.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.
Adds a default
SECURITY.md. GitHub uses this for every Development Seed repo that doesn't have its own, linking it from each repo's Security tab and the new-issue page.It directs reporters to GitHub's private vulnerability reporting instead of public issues and sets expectations for acknowledgement, advisories/CVEs, and supported versions.
Note: private vulnerability reporting is a per-repo setting (or can be enabled for all repos under org Settings → Code security). For repos where it's off, the policy tells reporters to request a private contact via an issue without disclosing details.
Related: developmentseed/stac-auth-proxy#218 (repo-specific policy).
🤖 Generated with Claude Code