Merge pull request #823 from plotly/add-security-policy

Create SECURITY.md

Author: scjody

SECURITY.md

@@ -0,0 +1,34 @@
+# plotly.js Security Policy
+
+The open source plotly.js library is provided "AS IS", with no security guarantees.  Please see our
+[license](https://raw.githubusercontent.com/plotly/plotly.js/master/LICENSE) for more information.
+
+In the 1.x releases of plotly.js, we attempt to protect against XSS attacks (and similar issues) resulting from
+untrusted data being graphed by plotly.js.  However, XSS or other issues may still exist.
+
+Note that the typical use case for plotly.js is for visualizing data from trusted sources.  For example if you use plotly.js to add a dashboard to your site and you control all the input data that's sent to plotly.js, you are not dependent on plotly.js for XSS protection.
+
+If you require a higher degree of assurance, please consider purchasing our
+[Plotly On-Premise](https://plot.ly/product/enterprise/) product, or [contact the Plotly sales team](mailto:[email protected])
+for more options.
+
+## Reports
+
+To report a security vulnerability, please email [email protected] with steps to reproduce the problem. Please allow up to
+24 hours for an initial response.
+
+## Bounties
+
+In some cases, we offer monetary compensation (bounties) for reports of security vulnerabilities.  Please see the [Plotly Security Vulnerability Bounty Program](http://help.plot.ly/security/) page for more information.
+
+## Release Process
+
+plotly.js security fixes are normally released as "patch" releases on top of the current plotly.js version.  For example if the current plotly.js version is 1.14.0 and we fix a security issue, we will release 1.14.1 with the fix.  Alternatively, security fixes may be made as part of a major or minor plotly.js release, if the fix coincides with our normal release cycle.  For example if the current plotly.js version is 1.14.0, we may release version 1.15.0 with the fix instead of 1.14.1.
+
+Security fixes are backported to older versions of plotly.js as required by paying Plotly On-Premise or Plotly Cloud customers.  These fixes are released as "patch" releases, and are made available to the community once affected customers have upgraded.  We also accept backports to older versions contributed by community members.
+
+Since the typical plotly.js use case involves trusted data, we do not remove old, potentially vulnerable versions from our GitHub repo or from our CDN.
+
+## Advisories
+
+All plotly.js security advisories released after August 1, 2016 are available at the [Plotly Security Advisories](http://help.plot.ly/security-advisories/) page.