source: trip-planner-front/node_modules/connect/SECURITY.md@ fa375fe

Last change on this file since fa375fe was 6a3a178, checked in by Ema <ema_spirova@…>, 3 years ago

initial commit

  • Property mode set to 100644
File size: 1.7 KB
Line 
1# Security Policies and Procedures
2
3This document outlines security procedures and general policies for the Connect
4project.
5
6 * [Reporting a Bug](#reporting-a-bug)
7 * [Disclosure Policy](#disclosure-policy)
8 * [Comments on this Policy](#comments-on-this-policy)
9
10## Reporting a Bug
11
12The Connect team and community take all security bugs in Connect seriously.
13Thank you for improving the security of Connect. We appreciate your efforts and
14responsible disclosure and will make every effort to acknowledge your
15contributions.
16
17Report security bugs by emailing the lead maintainer in the README.md file.
18
19The lead maintainer will acknowledge your email within 48 hours, and will send a
20more detailed response within 48 hours indicating the next steps in handling
21your report. After the initial reply to your report, the security team will
22endeavor to keep you informed of the progress towards a fix and full
23announcement, and may ask for additional information or guidance.
24
25Report security bugs in third-party modules to the person or team maintaining
26the module. You can also report a vulnerability through the
27[Node Security Project](https://nodesecurity.io/report).
28
29## Disclosure Policy
30
31When the security team receives a security bug report, they will assign it to a
32primary handler. This person will coordinate the fix and release process,
33involving the following steps:
34
35 * Confirm the problem and determine the affected versions.
36 * Audit code to find any potential similar problems.
37 * Prepare fixes for all releases still under maintenance. These fixes will be
38 released as fast as possible to npm.
39
40## Comments on this Policy
41
42If you have suggestions on how this process could be improved please submit a
43pull request.
Note: See TracBrowser for help on using the repository browser.