├── vulnerabilities_issues_created_log ├── arguments.py ├── constants.py ├── queries.py ├── NOTICE ├── Contributing.md ├── README.md ├── graph_ql.py ├── Code-of-Conduct └── LICENSE /vulnerabilities_issues_created_log: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /arguments.py: -------------------------------------------------------------------------------- 1 | # Copyright 2019, Oath Inc. 2 | # Licensed under the terms of the Apache 2.0 license. See LICENSE file in project root for terms. 3 | 4 | 5 | import sys 6 | 7 | graphql_authorization = sys.argv[1] 8 | jira_authorization = sys.argv[2] 9 | jira_url = sys.argv[3] 10 | jira_project_key = sys.argv[4] 11 | vulnerabilities_issue_created_track_path = sys.argv[5] 12 | -------------------------------------------------------------------------------- /constants.py: -------------------------------------------------------------------------------- 1 | # Copyright 2019, Oath Inc. 2 | # Licensed under the terms of the Apache 2.0 license. See LICENSE file in project root for terms. 3 | 4 | from arguments import jira_url 5 | from arguments import jira_authorization 6 | from arguments import graphql_authorization 7 | 8 | 9 | 10 | headers_graphql = { 11 | 'Accept': 'application/vnd.github.vixen-preview', 12 | 'Authorization': 'bearer %s' % (graphql_authorization), 13 | } 14 | 15 | headers_jira = { 16 | 'Content-Type': 'application/json', 17 | 'Authorization': 'Basic %s' %(jira_authorization) 18 | } 19 | 20 | graphql_url = "https://api.github.com/graphql" 21 | 22 | jira_url = "%s" %(jira_url) 23 | 24 | 25 | -------------------------------------------------------------------------------- /queries.py: -------------------------------------------------------------------------------- 1 | #Copyright 2019, Oath Inc. 2 | #Licensed under the terms of the Apache 2.0 license. See LICENSE file in root for terms. 3 | 4 | query = """{organization 5 | (login: "yahoo") 6 | {repositories(first:100) 7 | { edges 8 | { node 9 | {owner 10 | { id } 11 | name 12 | vulnerabilityAlerts ( first: 100 ) 13 | { edges 14 | { node 15 | { affectedRange 16 | dismissReason 17 | dismissedAt 18 | externalIdentifier 19 | externalReference 20 | fixedIn 21 | id 22 | packageName 23 | } 24 | } 25 | } 26 | } 27 | } 28 | } 29 | } 30 | }""" 31 | -------------------------------------------------------------------------------- /NOTICE: -------------------------------------------------------------------------------- 1 | GitHub Security Alert Automation 2 | Copyright 2019, Oath Inc. 3 | 4 | This project includes code developed by James Siri. 5 | Project link: https://github.com/jamesiri/github-cve-report-poc 6 | MIT License Copyright (c) 2019 James Siri 7 | 8 | Permission is hereby granted, free of charge, to any person obtaining a copy 9 | of this software and associated documentation files (the "Software"), to deal 10 | in the Software without restriction, including without limitation the rights 11 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 12 | copies of the Software, and to permit persons to whom the Software is 13 | furnished to do so, subject to the following conditions: 14 | 15 | The above copyright notice and this permission notice shall be included in all 16 | copies or substantial portions of the Software. 17 | 18 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 19 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 20 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 21 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 22 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 23 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 24 | SOFTWARE. 25 | -------------------------------------------------------------------------------- /Contributing.md: -------------------------------------------------------------------------------- 1 | # How to contribute 2 | First, thanks for taking the time to contribute to our project! The following information provides a guide for making contributions. 3 | 4 | ## Code of Conduct 5 | 6 | By participating in this project, you agree to abide by the [Oath Code of Conduct](Code-of-Conduct.md). Everyone is welcome to submit a pull request or open an issue to improve the documentation, add improvements, or report bugs. 7 | 8 | ## How to Ask a Question 9 | 10 | If you simply have a question that needs an answer, [create an issue](https://help.github.com/articles/creating-an-issue/), and label it as a question. 11 | 12 | ## How To Contribute 13 | 14 | ### Report a Bug or Request a Feature 15 | 16 | If you encounter any bugs while using this software, or want to request a new feature or enhancement, feel free to [create an issue](https://help.github.com/articles/creating-an-issue/) to report it, make sure you add a label to indicate what type of issue it is. 17 | 18 | ### Contribute Code 19 | Pull requests are welcome for bug fixes. If you want to implement something new, please [request a feature first](#report-a-bug-or-request-a-feature) so we can discuss it. 20 | 21 | #### Creating a Pull Request 22 | Please follow [best practices](https://github.com/trein/dev-best-practices/wiki/Git-Commit-Best-Practices) for creating git commits. 23 | 24 | When your code is ready to be submitted, you can [submit a pull request](https://help.github.com/articles/creating-a-pull-request/) to begin the code review process. 25 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | 2 | # GitHub Security Alerts Workflow 3 | 4 | This script is for teams that want to leverage GitHub Security Alerts into their workflow. It currently supports creating Jira tickets from the GitHub GraphQL API for security alerts. 5 | 6 | ## Table of Contents 7 | 8 | - [Background](#background) 9 | - [Install](#install) 10 | - [Configuration](#configuration) 11 | - [Usage](#usage) 12 | - [Contribute](#contribute) 13 | - [License](#license) 14 | 15 | ## Background 16 | 17 | This purpose of this project is to manage security vulnerabilities for open source projects using GitHub’s security alerts at scale. 18 | 19 | ## Install 20 | 21 | This script requires Python3 to run, so ensure you have this installed first. Installation of this script is as simple as the following: 22 | 23 | `git clone https://github.com/yahoo/GitHub-Security-Alerts-Workflow.git $$ cd GitHub-Security-Alerts-Workflow` 24 | 25 | ## Usage 26 | 27 | Use the following command to run this script: 28 | 29 | `python3 graph_ql.py graph_ql_authorization_key jira_authorization_key jira_url jira_project_key` 30 | 31 | * graph_ql_authorization_key - A GitHub GraphQL access token that has the ability to view security alerts for the chosen repo. 32 | * jira_authorization_key - An authorization key for your Jira instance with the ability to create and modify tickets. 33 | * jira_url - The endpoint for your Jira instance's issue API, e.g. https://jira.xyz.com/rest/api/2/issue/ 34 | * jira_project_key - The identifier key for the Jira project you want to create issues for. 35 | 36 | ## Contribute 37 | 38 | Please refer to [the contributing.md file](Contributing.md) for information about how to get involved. We welcome issues, questions, and pull requests. Pull Requests are welcome. 39 | 40 | ## Maintainers 41 | Manikandan Subramaniam: manikandan.subramaniam@verizonmedia.com
42 | Ashley Wolf: awolf@verizonmedia.com 43 | 44 | ## License 45 | 46 | This project is licensed under the terms of the [Apache 2.0](LICENSE-Apache-2.0) open source license. Please refer to [LICENSE](LICENSE) for the full terms. 47 | 48 | 49 | -------------------------------------------------------------------------------- /graph_ql.py: -------------------------------------------------------------------------------- 1 | # Copyright 2019, Oath Inc. 2 | # Licensed under the terms of the Apache 2.0 license. See LICENSE file in project root for terms. 3 | 4 | import requests 5 | import pprint 6 | from queries import query 7 | from constants import headers_graphql 8 | from constants import graphql_url 9 | from constants import jira_url 10 | from arguments import jira_project_key 11 | from constants import headers_jira 12 | from arguments import vulnerabilities_issue_created_track_path 13 | import json 14 | import collections 15 | 16 | # A simple function to use requests.post to make the API call. Note the json= section. 17 | 18 | 19 | def run_query(query): 20 | request = requests.post(graphql_url, json={'query': query}, headers=headers_graphql) 21 | if request.status_code == 200: 22 | return request.json() 23 | else: 24 | raise Exception("Query failed to run by returning code of {}. {}".format(request.status_code, query)) 25 | 26 | 27 | result = run_query(query) # Execute the query 28 | 29 | 30 | def get_vulnerabilities(): 31 | vulnerabilities_list = {} 32 | 33 | for edges in result['data']['organization']['repositories']['edges']: 34 | for vulIssues in edges['node']['vulnerabilityAlerts']['edges']: 35 | vulnerable_repo_name = edges['node']['name'] 36 | if vulnerable_repo_name not in vulnerabilities_list: 37 | vulnerabilities_list[vulnerable_repo_name] = set() 38 | vulnerabilities = vulIssues['node']['packageName'] 39 | vulnerabilities_list[vulnerable_repo_name].add(vulnerabilities) 40 | return vulnerabilities_list 41 | 42 | 43 | ordered_vulnerabilities_list = collections.OrderedDict(get_vulnerabilities()) 44 | print(ordered_vulnerabilities_list) 45 | 46 | res = ordered_vulnerabilities_list 47 | vulnerabilities_keys_list = list(res.keys()) 48 | vulnerabilities_values_list = list(res.values()) 49 | 50 | 51 | vulnerabilities_issues_created_keys_list = [] 52 | vulnerabilities_issues_created_values_list = [] 53 | 54 | 55 | def create_jira_issue(): 56 | for i in range(0,len(vulnerabilities_keys_list)): 57 | 58 | if vulnerabilities_keys_list[i] not in vulnerabilities_issues_created_keys_list and \ 59 | vulnerabilities_values_list[i] not in vulnerabilities_issues_created_values_list and \ 60 | vulnerabilities_keys_list[i] not in open(vulnerabilities_issue_created_track_path).read(): 61 | 62 | issue_body = {"fields": { 63 | "project": 64 | { 65 | "key": "%s" % (jira_project_key) 66 | }, 67 | "summary": "Security vulnerability issues found in project %s" % (vulnerabilities_keys_list[i]), 68 | "description": "Following are the list of vulnerabilities found for the above project %s" % 69 | (vulnerabilities_values_list[i]), 70 | "issuetype": { 71 | "name": "Defect" 72 | } 73 | } 74 | } 75 | 76 | issue_body_data = json.dumps(issue_body) 77 | request = requests.post(jira_url, data=issue_body_data, headers=headers_jira) 78 | 79 | vulnerabilities_issues_created_keys_list.append(vulnerabilities_keys_list[i]) 80 | vulnerabilities_issues_created_values_list.append(vulnerabilities_values_list[i]) 81 | 82 | tracked_repos = '\n'.join(vulnerabilities_issues_created_keys_list) 83 | 84 | f = open(vulnerabilities_issue_created_track_path, "w") 85 | f.write(tracked_repos) 86 | 87 | if request.status_code == 201: 88 | print(request.json()) 89 | 90 | else: 91 | raise Exception("Issue failed to be created by returning code of {}. {}".format(request.status_code, 92 | request.json())) 93 | 94 | if len(vulnerabilities_issues_created_keys_list) == len(vulnerabilities_keys_list) and\ 95 | len(vulnerabilities_issues_created_values_list) == len(vulnerabilities_values_list): 96 | return True 97 | else: 98 | continue 99 | 100 | 101 | ans = create_jira_issue() 102 | print(len(vulnerabilities_issues_created_keys_list)) 103 | -------------------------------------------------------------------------------- /Code-of-Conduct: -------------------------------------------------------------------------------- 1 | # Verizon Media Open Source Code of Conduct 2 | 3 | ## Summary 4 | This Code of Conduct is our way to encourage good behavior and discourage bad behavior in our open source community. We invite participation from many people to bring different perspectives to support this project. We pledge to do our part to foster a welcoming and professional environment free of harassment. We expect participants to communicate professionally and thoughtfully during their involvement with this project. 5 | 6 | Participants may lose their good standing by engaging in misconduct. For example: insulting, threatening, or conveying unwelcome sexual content. We ask participants who observe conduct issues to report the incident directly to the project's Response Team at opensource-conduct@verizonmedia.com. Verizon Media will assign a respondent to address the issue. We may remove harassers from this project. 7 | 8 | This code does not replace the terms of service or acceptable use policies of the websites used to support this project. We acknowledge that participants may be subject to additional conduct terms based on their employment which may govern their online expressions. 9 | 10 | ## Details 11 | This Code of Conduct makes our expectations of participants in this community explicit. 12 | * We forbid harassment and abusive speech within this community. 13 | * We request participants to report misconduct to the project’s Response Team. 14 | * We urge participants to refrain from using discussion forums to play out a fight. 15 | 16 | ### Expected Behaviors 17 | We expect participants in this community to conduct themselves professionally. Since our primary mode of communication is text on an online forum (e.g. issues, pull requests, comments, emails, or chats) devoid of vocal tone, gestures, or other context that is often vital to understanding, it is important that participants are attentive to their interaction style. 18 | 19 | * **Assume positive intent.** We ask community members to assume positive intent on the part of other people’s communications. We may disagree on details, but we expect all suggestions to be supportive of the community goals. 20 | * **Respect participants.** We expect participants will occasionally disagree. Even if we reject an idea, we welcome everyone’s participation. Open Source projects are learning experiences. Ask, explore, challenge, and then respectfully assert if you agree or disagree. If your idea is rejected, be more persuasive not bitter. 21 | * **Welcoming to new members.** New members bring new perspectives. Some may raise questions that have been addressed before. Kindly point them to existing discussions. Everyone is new to every project once. 22 | * **Be kind to beginners.** Beginners use open source projects to get experience. They might not be talented coders yet, and projects should not accept poor quality code. But we were all beginners once, and we need to engage kindly. 23 | * **Consider your impact on others.** Your work will be used by others, and you depend on the work of others. We expect community members to be considerate and establish a balance their self-interest with communal interest. 24 | * **Use words carefully.** We may not understand intent when you say something ironic. Poe’s Law suggests that without an emoticon people will misinterpret sarcasm. We ask community members to communicate plainly. 25 | * **Leave with class.** When you wish to resign from participating in this project for any reason, you are free to fork the code and create a competitive project. Open Source explicitly allows this. Your exit should not be dramatic or bitter. 26 | 27 | ### Unacceptable Behaviors 28 | Participants remain in good standing when they do not engage in misconduct or harassment. To elaborate: 29 | * **Don't be a bigot.** Calling out project members by their identity or background in a negative or insulting manner. This includes, but is not limited to, slurs or insinuations related to protected or suspect classes e.g. race, color, citizenship, national origin, political belief, religion, sexual orientation, gender identity and expression, age, size, culture, ethnicity, genetic features, language, profession, national minority statue, mental or physical ability. 30 | * **Don't insult.** Insulting remarks about a person’s lifestyle practices. 31 | * **Don't dox.** Revealing private information about other participants without explicit permission. 32 | * **Don't intimidate.** Threats of violence or intimidation of any project member. 33 | * **Don't creep.** Unwanted sexual attention or content unsuited for the subject of this project. 34 | * **Don't disrupt.** Sustained disruptions in a discussion. 35 | * **Let us help.** Refusal to assist the Response Team to resolve an issue in the community. 36 | 37 | We do not list all forms of harassment, nor imply some forms of harassment are not worthy of action. Any participant who *feels* harassed or *observes* harassment, should report the incident. Victim of harassment should not address grievances in the public forum, as this often intensifies the problem. Report it, and let us address it off-line. 38 | 39 | ### Reporting Issues 40 | If you experience or witness misconduct, or have any other concerns about the conduct of members of this project, please report it by contacting our Response Team at opensource-conduct@verizonmedia.com who will handle your report with discretion. Your report should include: 41 | * Your preferred contact information. We cannot process anonymous reports. 42 | * Names (real or usernames) of those involved in the incident. 43 | * Your account of what occurred, and if the incident is ongoing. Please provide links to or transcripts of the publicly available records (e.g. a mailing list archive or a public IRC logger), so that we can review it. 44 | * Any additional information that may be helpful to achieve resolution. 45 | 46 | After filing a report, a representative will contact you directly to review the incident and ask additional questions. If a member of the Verizon Media Response Team is named in an incident report, that member will be recused from handling your incident. If the complaint originates from a member of the Response Team, it will be addressed by a different member of the Response Team. We will consider reports to be confidential for the purpose of protecting victims of abuse. 47 | 48 | ### Scope 49 | Verizon Media will assign a Response Team member with admin rights on the project and legal rights on the project copyright. The Response Team is empowered to restrict some privileges to the project as needed. Since this project is governed by an open source license, any participant may fork the code under the terms of the project license. The Response Team’s goal is to preserve the project if possible, and will restrict or remove participation from those who disrupt the project. 50 | 51 | This code does not replace the terms of service or acceptable use policies that are provided by the websites used to support this community. Nor does this code apply to communications or actions that take place outside of the context of this community. Many participants in this project are also subject to codes of conduct based on their employment. This code is a social-contract that informs participants of our social expectations. It is not a terms of service or legal contract. 52 | 53 | ## License and Acknowledgment. 54 | This text is shared under the [CC-BY-4.0 license](https://creativecommons.org/licenses/by/4.0/). This code is based on a study conducted by the [TODO Group](https://todogroup.org/) of many codes used in the open source community. If you have feedback about this code, contact our Response Team at the address listed above. 55 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | Apache License 2 | Version 2.0, January 2004 3 | http://www.apache.org/licenses/ 4 | 5 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 6 | 7 | 1. Definitions. 8 | 9 | "License" shall mean the terms and conditions for use, reproduction, 10 | and distribution as defined by Sections 1 through 9 of this document. 11 | 12 | "Licensor" shall mean the copyright owner or entity authorized by 13 | the copyright owner that is granting the License. 14 | 15 | "Legal Entity" shall mean the union of the acting entity and all 16 | other entities that control, are controlled by, or are under common 17 | control with that entity. For the purposes of this definition, 18 | "control" means (i) the power, direct or indirect, to cause the 19 | direction or management of such entity, whether by contract or 20 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 21 | outstanding shares, or (iii) beneficial ownership of such entity. 22 | 23 | "You" (or "Your") shall mean an individual or Legal Entity 24 | exercising permissions granted by this License. 25 | 26 | "Source" form shall mean the preferred form for making modifications, 27 | including but not limited to software source code, documentation 28 | source, and configuration files. 29 | 30 | "Object" form shall mean any form resulting from mechanical 31 | transformation or translation of a Source form, including but 32 | not limited to compiled object code, generated documentation, 33 | and conversions to other media types. 34 | 35 | "Work" shall mean the work of authorship, whether in Source or 36 | Object form, made available under the License, as indicated by a 37 | copyright notice that is included in or attached to the work 38 | (an example is provided in the Appendix below). 39 | 40 | "Derivative Works" shall mean any work, whether in Source or Object 41 | form, that is based on (or derived from) the Work and for which the 42 | editorial revisions, annotations, elaborations, or other modifications 43 | represent, as a whole, an original work of authorship. For the purposes 44 | of this License, Derivative Works shall not include works that remain 45 | separable from, or merely link (or bind by name) to the interfaces of, 46 | the Work and Derivative Works thereof. 47 | 48 | "Contribution" shall mean any work of authorship, including 49 | the original version of the Work and any modifications or additions 50 | to that Work or Derivative Works thereof, that is intentionally 51 | submitted to Licensor for inclusion in the Work by the copyright owner 52 | or by an individual or Legal Entity authorized to submit on behalf of 53 | the copyright owner. For the purposes of this definition, "submitted" 54 | means any form of electronic, verbal, or written communication sent 55 | to the Licensor or its representatives, including but not limited to 56 | communication on electronic mailing lists, source code control systems, 57 | and issue tracking systems that are managed by, or on behalf of, the 58 | Licensor for the purpose of discussing and improving the Work, but 59 | excluding communication that is conspicuously marked or otherwise 60 | designated in writing by the copyright owner as "Not a Contribution." 61 | 62 | "Contributor" shall mean Licensor and any individual or Legal Entity 63 | on behalf of whom a Contribution has been received by Licensor and 64 | subsequently incorporated within the Work. 65 | 66 | 2. Grant of Copyright License. Subject to the terms and conditions of 67 | this License, each Contributor hereby grants to You a perpetual, 68 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 69 | copyright license to reproduce, prepare Derivative Works of, 70 | publicly display, publicly perform, sublicense, and distribute the 71 | Work and such Derivative Works in Source or Object form. 72 | 73 | 3. Grant of Patent License. Subject to the terms and conditions of 74 | this License, each Contributor hereby grants to You a perpetual, 75 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 76 | (except as stated in this section) patent license to make, have made, 77 | use, offer to sell, sell, import, and otherwise transfer the Work, 78 | where such license applies only to those patent claims licensable 79 | by such Contributor that are necessarily infringed by their 80 | Contribution(s) alone or by combination of their Contribution(s) 81 | with the Work to which such Contribution(s) was submitted. If You 82 | institute patent litigation against any entity (including a 83 | cross-claim or counterclaim in a lawsuit) alleging that the Work 84 | or a Contribution incorporated within the Work constitutes direct 85 | or contributory patent infringement, then any patent licenses 86 | granted to You under this License for that Work shall terminate 87 | as of the date such litigation is filed. 88 | 89 | 4. Redistribution. You may reproduce and distribute copies of the 90 | Work or Derivative Works thereof in any medium, with or without 91 | modifications, and in Source or Object form, provided that You 92 | meet the following conditions: 93 | 94 | (a) You must give any other recipients of the Work or 95 | Derivative Works a copy of this License; and 96 | 97 | (b) You must cause any modified files to carry prominent notices 98 | stating that You changed the files; and 99 | 100 | (c) You must retain, in the Source form of any Derivative Works 101 | that You distribute, all copyright, patent, trademark, and 102 | attribution notices from the Source form of the Work, 103 | excluding those notices that do not pertain to any part of 104 | the Derivative Works; and 105 | 106 | (d) If the Work includes a "NOTICE" text file as part of its 107 | distribution, then any Derivative Works that You distribute must 108 | include a readable copy of the attribution notices contained 109 | within such NOTICE file, excluding those notices that do not 110 | pertain to any part of the Derivative Works, in at least one 111 | of the following places: within a NOTICE text file distributed 112 | as part of the Derivative Works; within the Source form or 113 | documentation, if provided along with the Derivative Works; or, 114 | within a display generated by the Derivative Works, if and 115 | wherever such third-party notices normally appear. The contents 116 | of the NOTICE file are for informational purposes only and 117 | do not modify the License. You may add Your own attribution 118 | notices within Derivative Works that You distribute, alongside 119 | or as an addendum to the NOTICE text from the Work, provided 120 | that such additional attribution notices cannot be construed 121 | as modifying the License. 122 | 123 | You may add Your own copyright statement to Your modifications and 124 | may provide additional or different license terms and conditions 125 | for use, reproduction, or distribution of Your modifications, or 126 | for any such Derivative Works as a whole, provided Your use, 127 | reproduction, and distribution of the Work otherwise complies with 128 | the conditions stated in this License. 129 | 130 | 5. Submission of Contributions. Unless You explicitly state otherwise, 131 | any Contribution intentionally submitted for inclusion in the Work 132 | by You to the Licensor shall be under the terms and conditions of 133 | this License, without any additional terms or conditions. 134 | Notwithstanding the above, nothing herein shall supersede or modify 135 | the terms of any separate license agreement you may have executed 136 | with Licensor regarding such Contributions. 137 | 138 | 6. Trademarks. This License does not grant permission to use the trade 139 | names, trademarks, service marks, or product names of the Licensor, 140 | except as required for reasonable and customary use in describing the 141 | origin of the Work and reproducing the content of the NOTICE file. 142 | 143 | 7. Disclaimer of Warranty. Unless required by applicable law or 144 | agreed to in writing, Licensor provides the Work (and each 145 | Contributor provides its Contributions) on an "AS IS" BASIS, 146 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 147 | implied, including, without limitation, any warranties or conditions 148 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 149 | PARTICULAR PURPOSE. You are solely responsible for determining the 150 | appropriateness of using or redistributing the Work and assume any 151 | risks associated with Your exercise of permissions under this License. 152 | 153 | 8. Limitation of Liability. In no event and under no legal theory, 154 | whether in tort (including negligence), contract, or otherwise, 155 | unless required by applicable law (such as deliberate and grossly 156 | negligent acts) or agreed to in writing, shall any Contributor be 157 | liable to You for damages, including any direct, indirect, special, 158 | incidental, or consequential damages of any character arising as a 159 | result of this License or out of the use or inability to use the 160 | Work (including but not limited to damages for loss of goodwill, 161 | work stoppage, computer failure or malfunction, or any and all 162 | other commercial damages or losses), even if such Contributor 163 | has been advised of the possibility of such damages. 164 | 165 | 9. Accepting Warranty or Additional Liability. While redistributing 166 | the Work or Derivative Works thereof, You may choose to offer, 167 | and charge a fee for, acceptance of support, warranty, indemnity, 168 | or other liability obligations and/or rights consistent with this 169 | License. However, in accepting such obligations, You may act only 170 | on Your own behalf and on Your sole responsibility, not on behalf 171 | of any other Contributor, and only if You agree to indemnify, 172 | defend, and hold each Contributor harmless for any liability 173 | incurred by, or claims asserted against, such Contributor by reason 174 | of your accepting any such warranty or additional liability. 175 | 176 | END OF TERMS AND CONDITIONS 177 | --------------------------------------------------------------------------------