move templates to .github folder

ISSUE_TEMPLATE/BUG_REPORT.md → .github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -1,5 +1,5 @@
 ---
-name: "🐞 Bug report"
+name: "Bug report"
 about: Report an issue with this package
 title: ''
 labels: ''

ISSUE_TEMPLATE/FEATURE_REQUEST.md → .github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -1,5 +1,5 @@
 ---
-name: "🚀 Feature request"
+name: "Feature request"
 about: Request a new feature to be added
 title: ''
 labels: ''

ISSUE_TEMPLATE/SECURITY.md → .github/ISSUE_TEMPLATE/SECURITY.md

@@ -1,5 +1,5 @@
 ---
-name: "⛔ Security issue"
+name: "Security issue"
 about: Please file security issues at https://github.com/standard/standard/blob/master/SECURITY.md
 title: ''
 labels: ''

SECURITY.md

@@ -0,0 +1,42 @@
+# Security Policies and Procedures
+
+This document outlines security procedures and general policies for the `standard`
+project.
+
+  * [Reporting a Bug](#reporting-a-bug)
+  * [Disclosure Policy](#disclosure-policy)
+  * [Comments on this Policy](#comments-on-this-policy)
+
+## Reporting a Bug
+
+The `standard` team and community take all security bugs in `standard` seriously.
+Thank you for improving the security of `standard`. We appreciate your efforts and
+responsible disclosure and will make every effort to acknowledge your
+contributions.
+
+Report security bugs by emailing the lead maintainer at [email protected].
+
+The lead maintainer will acknowledge your email within 48 hours, and will send a
+more detailed response within 48 hours indicating the next steps in handling
+your report. After the initial reply to your report, the security team will
+endeavor to keep you informed of the progress towards a fix and full
+announcement, and may ask for additional information or guidance.
+
+Report security bugs in third-party modules to the person or team maintaining
+the module.
+
+## Disclosure Policy
+
+When the security team receives a security bug report, they will assign it to a
+primary handler. This person will coordinate the fix and release process,
+involving the following steps:
+
+  * Confirm the problem and determine the affected versions.
+  * Audit code to find any potential similar problems.
+  * Prepare fixes for all releases still under maintenance. These fixes will be
+    released as fast as possible to npm.
+
+## Comments on this Policy
+
+If you have suggestions on how this process could be improved please submit a
+pull request.