Add security policy document #1426
Merged
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
Relequestual
requested review from
karenetheridge,
Julian,
awwright,
jdesrosiers and
gregsdennis
and removed request for
a team
Julian
approved these changes
Aug 9, 2023
gregsdennis
approved these changes
Aug 9, 2023
jdesrosiers
approved these changes
Aug 9, 2023
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.
Resolves json-schema-org/community#351
We have already previously enabled security reporting on the spec repo.
While I made it clear that people should not report impelementation security concerns here, I wanted to also offer potential help to implementers who might get reports.
I can't imagine we would get any reports given the repos/projects we currently have, although that could change in the future, and this is a requirement of the OpenJS Foundation onboarding process.