Repository navigation
Add a .well-known/security.txt - #3205
Merged
Merged
Conversation
JacobCoffee
approved these changes
Oct 30, 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
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.
This adds a
security.txtfile, as specified by RFC 9116 and securitytxt.org. Technically, they want an expiry date that's less than one year away, but there's no need for us to update it that frequently so I picked 2030. I also opted to pointContact(required) to our policy rather than the email directly.Although I doubt this will increase the quality of reports, maybe it will point more users to the policy where they'll see we have no bug bounty and won't waste our time with bogus reports... but that's unlikely. :-( However, it's still good practice to have this information recorded clearly.
CC @sethmlarson @JacobCoffee