Add SECURITY.md #2887
Open
Add SECURITY.md #2887
+24
−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
This adds a SECURITY.md file that outlines the supported versions for security updates and provides instructions for reporting security vulnerabilities. The document specifies that version 2.20 is currently supported, and directs users to report vulnerabilities via email rather than through GitHub Issues.
This updates the SECURITY.md file to mark versions 2.18 and 2.19 as supported in addition to 2.20, adds links to the release tags for each version, consolidates unsupported versions to "<=2.17", and replaces the placeholder email address with thewebworkproject@gmail.com for reporting security vulnerabilities.
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.
There’s currently no SECURITY.md in the repository root. Since WeBWorK is used by multiple universities for graded assignments, having a clear security reporting path matters—publicly disclosed vulnerabilities could impact the integrity of assignments and course outcomes.
I recommend adding a standard SECURITY.md to enable GitHub vulnerability reporting and to provide clear guidance on how to responsibly report issues (what details to include, expected response times, and where to report). GitHub’s guidance is here:
https://docs.github.com/en/code-security/how-tos/report-and-fix-vulnerabilities/configure-vulnerability-reporting/adding-a-security-policy-to-your-repository
PS: The file changed is an example, and should be replaced with the actual security policy.