aboutsummaryrefslogtreecommitdiff
path: root/node_modules/cookie/SECURITY.md
diff options
context:
space:
mode:
authorgrant-kun <[email protected]>2022-09-26 07:14:29 -0500
committergrant-kun <[email protected]>2022-09-26 07:14:29 -0500
commit86feb9e6403cfa6198ffb6895877c1c00d2a738a (patch)
treecf29210132c5ffb2be80afe04eb0fa231dac3382 /node_modules/cookie/SECURITY.md
parent47e3ae49258f9ddfb91b570745fedeaef4f0fc8f (diff)
update (not working)
Diffstat (limited to 'node_modules/cookie/SECURITY.md')
-rw-r--r--node_modules/cookie/SECURITY.md25
1 files changed, 25 insertions, 0 deletions
diff --git a/node_modules/cookie/SECURITY.md b/node_modules/cookie/SECURITY.md
new file mode 100644
index 0000000..fd4a6c5
--- /dev/null
+++ b/node_modules/cookie/SECURITY.md
@@ -0,0 +1,25 @@
+# Security Policies and Procedures
+
+## Reporting a Bug
+
+The `cookie` team and community take all security bugs seriously. Thank
+you for improving the security of the project. We appreciate your efforts and
+responsible disclosure and will make every effort to acknowledge your
+contributions.
+
+Report security bugs by emailing the current owner(s) of `cookie`. This
+information can be found in the npm registry using the command
+`npm owner ls cookie`.
+If unsure or unable to get the information from the above, open an issue
+in the [project issue tracker](https://github.com/jshttp/cookie/issues)
+asking for the current contact information.
+
+To ensure the timely response to your report, please ensure that the entirety
+of the report is contained within the email body and not solely behind a web
+link or an attachment.
+
+At least one owner 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 owners will
+endeavor to keep you informed of the progress towards a fix and full
+announcement, and may ask for additional information or guidance.