Add /.well-known/security.txt (RFC 9116)#1222
Open
kobihikri wants to merge 1 commit into
Open
Conversation
react-hook-form.com serves no security.txt at the well-known location, so a researcher following RFC 9116 has no machine-discoverable pointer to the project's security-reporting process. This adds one (served from public/). Signed-off-by: kobihikri <kobi.hikri@gmail.com>
✅ Deploy Preview for sage-cassata-31d224 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
@kobihikri is attempting to deploy a commit to the BEEKAI OSS Team on Vercel. A member of the Team first needs to authorize it. |
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.
What
Add
/.well-known/security.txtso the site serves one at the location RFC 9116 defines.Why
https://react-hook-form.com/.well-known/security.txt currently returns 404. RFC 9116 makes
/.well-known/security.txtthe standard, machine-discoverable place a security researcher (or automated tooling) looks first to learn how to report an issue. The file is added under the site's static directory (served verbatim), pointsContactat the project's GitHub Security Advisory intake, and carries a futureExpiresper §2.5.5.I used AI assistance to help identify this and draft the file; I verified the RFC reference and the live 404 myself and take responsibility for it.