1# Security Guidelines
 2
 3Please contact us directly at **security@3rd-Eden.com** for any bug that might
 4impact the security of this project. Please prefix the subject of your email
 5with `[security]` in lowercase and square brackets. Our email filters will
 6automatically prevent these messages from being moved to our spam box.
 7
 8You will receive an acknowledgement of your report within **24 hours**.
 9
10All emails that do not include security vulnerabilities will be removed and
11blocked instantly.
12
13## Exceptions
14
15If you do not receive an acknowledgement within the said time frame please give
16us the benefit of the doubt as it's possible that we haven't seen it yet. In
17this case please send us a message **without details** using one of the
18following methods:
19
20- Contact the lead developers of this project on their personal e-mails. You
21  can find the e-mails in the git logs, for example using the following command:
22  `git --no-pager show -s --format='%an <%ae>' <gitsha>` where `<gitsha>` is the
23  SHA1 of their latest commit in the project.
24- Create a GitHub issue stating contact details and the severity of the issue.
25
26Once we have acknowledged receipt of your report and confirmed the bug
27ourselves we will work with you to fix the vulnerability and publicly acknowledge
28your responsible disclosure, if you wish. In addition to that we will report
29all vulnerabilities to the [Node Security Project](https://nodesecurity.io/).
30
31## History
32
3304 Jan 2016: [Buffer vulnerablity](https://github.com/websockets/ws/releases/tag/1.0.1)