Conversation
✅ Deploy Preview for eager-borg-83c1a5 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jescalada
changed the title
TheJuanAndOnly99
requested changes
Sep 17, 2026
TheJuanAndOnly99
left a comment
TheJuanAndOnly99
left a comment
Member
There was a problem hiding this comment.
Hi @jescalada this is amazing, thank you! I made just 1 small suggested change.
|  | ||
|
|
||
| 3. Follow the submission steps in the project's security policy. Usually, this means clicking the "Report a vulnerability" button and filling in the [requested details](#details-to-include). | ||
| 4. If the project doesn't have a SECURITY.md policy available, submit the vulnerability via email to a project Maintainer (ideally, the Lead Maintainer). You can find contact emails in the project's `MAINTAINERS.md` file. Also, CC the email to [security@finos.org](mailto:security@finos.org). |
Member
There was a problem hiding this comment.
Suggested change
| 4. If the project doesn't have a SECURITY.md policy available, submit the vulnerability via email to a project Maintainer (ideally, the Lead Maintainer). You can find contact emails in the project's `MAINTAINERS.md` file. Also, CC the email to [security@finos.org](mailto:security@finos.org). | |
| 4. If the project doesn't have a SECURITY.md policy available and the "Report a vulnerability" button is not enabled, submit the vulnerability via email to a project Maintainer (ideally, the Lead Maintainer). You can find contact emails in the project's `MAINTAINERS.md` file. Also, CC the email to [security@finos.org](mailto:security@finos.org). |
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.
This PR simplifies some of the existing wording, adds standards (such as a
SECURITY.mdtemplate) and rewrites a few sections to reflect the new, native GitHub vulnerability disclosure process.I've used GitProxy as an example here and there, because it already has battle-tested security and release tooling for other projects to benefit.
Feel free to edit the wording wherever appropriate, and fill in anything I might have missed!