Skip to content

docs: add escalation policy #35

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
UlisesGascon wants to merge 1 commit into
base: master
Choose a base branch
from
+7 −0
Open

docs: add escalation policy #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@ project.
* [Reporting a Bug or Security Vulnerability](#reporting-a-bug-or-security-vulnerability)
* [Disclosure Policy](#disclosure-policy)
* [Comments on this Policy](#comments-on-this-policy)
* [escalate to the OpenJS Foundation CNA](#escalate-to-the-openjs-foundation-cna)

## Reporting a Bug or Security Vulnerability

Expand Down Expand Up @@ -71,3 +72,9 @@ involving the following steps:

If you have suggestions on how this process could be improved please submit a
pull request.

# Escalate to the OpenJS Foundation CNA

If you do not receive an acknowledgement of your report within **6 business days**, or if you cannot find a private security contact for the project, you may **escalate to the OpenJS Foundation CNA** at `security@lists.openjsf.org`.

If the project acknowledges your report but does not provide any further response or engagement within **14 days**, escalation is also appropriate.