From ed345dcf6bf8b0057600c900e5a33f423d33290c Mon Sep 17 00:00:00 2001 From: Uttam Krishna Ukkoji Date: Wed, 13 Apr 2022 13:51:33 +0530 Subject: [PATCH] Security file added License updated --- .gitignore | 3 ++- LICENSE.txt | 2 +- SECURITY.md | 27 +++++++++++++++++++++++++++ 3 files changed, 30 insertions(+), 2 deletions(-) create mode 100644 SECURITY.md diff --git a/.gitignore b/.gitignore index f7e55780..c5fe1836 100644 --- a/.gitignore +++ b/.gitignore @@ -11,4 +11,5 @@ tap-html.html *html-report coverage .env -.dccache \ No newline at end of file +.dccache +dist/* \ No newline at end of file diff --git a/LICENSE.txt b/LICENSE.txt index 91b787b1..0ec62c74 100755 --- a/LICENSE.txt +++ b/LICENSE.txt @@ -1,7 +1,7 @@ The MIT License (MIT) -Copyright (c) 2016-2021 Contentstack +Copyright (c) 2016-2022 Contentstack Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 00000000..b5fe070e --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,27 @@ +## Security + +Contentstack takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations. + +If you believe you have found a security vulnerability in any Contentstack-owned repository, please report it to us as described below. + +## Reporting Security Issues + +**Please do not report security vulnerabilities through public GitHub issues.** + +Send email to [security@contentstack.com](mailto:security@contentstack.com). + +You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. + +Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue: + + * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) + * Full paths of source file(s) related to the manifestation of the issue + * The location of the affected source code (tag/branch/commit or direct URL) + * Any special configuration required to reproduce the issue + * Step-by-step instructions to reproduce the issue + * Proof-of-concept or exploit code (if possible) + * Impact of the issue, including how an attacker might exploit the issue + +This information will help us triage your report more quickly. + +[https://www.contentstack.com/trust/](https://www.contentstack.com/trust/)