Add spec about security policy #390
Open
+85
−0
Conversation
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
mihaimaruseac
added a commit
to mihaimaruseac/specs
that referenced
this pull request
May 14, 2025
I used SPEC 11 name as that was selected from the last year, but I am happy to switch to a different number if needed. This is to be paired with scientific-python#390 and currently a draft.
mihaimaruseac
added a commit
to mihaimaruseac/specs
that referenced
this pull request
May 14, 2025
I used SPEC 11 name as that was selected from the last year, but I am happy to switch to a different number if needed. This is to be paired with scientific-python#390 and currently a draft. Signed-off-by: Mihai Maruseac <[email protected]>
mihaimaruseac
added a commit
to mihaimaruseac/specs
that referenced
this pull request
May 14, 2025
I used SPEC 11 name as that was selected from the last year, but I am happy to switch to a different number if needed. This is to be paired with scientific-python#390 and currently a draft. Signed-off-by: Mihai Maruseac <[email protected]>
mihaimaruseac
added a commit
to mihaimaruseac/specs
that referenced
this pull request
May 14, 2025
I used SPEC 11 name as that was selected from the last year, but I am happy to switch to a different number if needed. This is to be paired with scientific-python#390 and currently a draft. Signed-off-by: Mihai Maruseac <[email protected]>
mihaimaruseac
added a commit
to mihaimaruseac/specs
that referenced
this pull request
May 14, 2025
I used SPEC 11 name as that was selected from the last year, but I am happy to switch to a different number if needed. This is to be paired with scientific-python#390 and currently a draft. Signed-off-by: Mihai Maruseac <[email protected]>
tupui
approved these changes
Jun 11, 2025
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 PR introduces a new SPEC focused on Security Policy.
The SPEC outlines how projects can create and maintain a clear and accessible SECURITY.md file to guide users on how to report vulnerabilities responsibly and enable maintainers to respond effectively.
There have been ongoing conversations in the community, particularly at the Developer Summit 2024 and Developer Summit 2025 about improving how we handle vulnerability disclosure. A key part of that is making sure users know how to report issues properly and that starts with a clear security policy.
Due to the complexity of the broader disclosure process, we decided to split the work into two separate SPECs:
Security Policy (this PR)
Vulnerability Disclosure Process (coming soon in a PR by @mihaimaruseac )
A lot of the projects in the ecosystem already have a security policy but this SPEC will hopefully encourage more of them to adopt it.
Link to issue
Discourse post