chore: remove SECURITY.md in favor of org-wide policy#1494
Merged
Conversation
QuintinWillison
approved these changes
Jun 29, 2026
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.
What
Removes this repo's
SECURITY.mdso it inherits the organization-wide security policy maintained centrally insupabase/.github.References supabase/.github#20
Why
The security policy is being consolidated into a single org-wide default (
supabase/.github) instead of being duplicated across every repository. GitHub serves that default as the "Security policy" for any repo that doesn't define its own, so this file is now redundant.Note
Please do not merge until supabase/.github#20 is merged, otherwise this repo would briefly show no security policy.