Merge branch 'gh-pages' into mit-0

.github/workflows/test.yml

@@ -1,6 +1,10 @@
 name: Build and Test
 
-on: [push, pull_request]
+on:
+  push:
+    branches: [gh-pages]
+  pull_request:
+    branches: [gh-pages]
 
 jobs:
   test:
@@ -14,9 +18,7 @@ jobs:
       uses: ruby/setup-ruby@v1
       with:
         ruby-version: 2.7.1
-
-    - name: Install dependencies
-      run: ./script/bootstrap
+        bundler-cache: true
 
     - name: Run tests
       run: ./script/cibuild

CONTRIBUTING.md

@@ -1,4 +1,4 @@
-# How to Contribute
+# How to contribute
 
 We love Pull Requests! Your contributions help make ChooseALicense.com great.
 
@@ -6,7 +6,7 @@ Contributions to this project are [released](https://help.github.com/articles/gi
 
 Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
 
-## Getting Started
+## Getting started
 
 So you want to contribute to ChooseALicense. Great! We welcome any help we can
 get. But first, please make sure you understand what
@@ -34,7 +34,7 @@ If your proposed license meets the above criteria, here's a few other things to
 * The text of the license should match the corresponding text found in [spdx/license-list-data](https://github.com/spdx/license-list-data/blob/master/text/). If there are errors there, please fix them in [spdx/license-list-XML](https://github.com/spdx/license-list-XML) (from which the plain text version is generated) so as to minimize license text variation and make it easier for choosealicense.com to eventually consume license texts directly from SPDX.
 * The body of the file should be the text of the license in plain text.
 
-## Making Changes
+## Making changes
 
 The easiest way to make a change is to simply edit a file from your browser.
 When you click the edit button, it will fork the repository under your account.

LICENSE.md

@@ -1,4 +1,4 @@
-Copyright (c) 2013-2018 GitHub, Inc. and contributors
+Copyright (c) 2013-2021 GitHub, Inc. and contributors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

README.md

@@ -12,7 +12,7 @@ We catalog [select](CONTRIBUTING.md#adding-a-license) open source licenses with
 * Collaborate with and reinforce other licensing best practices and standards projects.
 * Not comprehensive. Seems like an odd goal, but there are a bajillion licenses out there. We're going to have to filter that down to a small list of those that matter.
 
-## Run It On Your Machine
+## Run it on your machine
 
 ### Managing Dependencies
 
@@ -54,7 +54,7 @@ Licenses sit in the `/_licenses` folder. Each license has YAML front matter desc
 * `spdx-id` - Short identifier specified by https://spdx.org/licenses/
 * `description` - A human-readable description of the license
 * `how` - Instructions on how to implement the license
-* `using` - A list of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/licensee/licensee) in the form of `project_name: license_file_url`
+* `using` - A map of 3 notable projects using the license with straightforward LICENSE files which serve as examples newcomers can follow and that can be detected by [licensee](https://github.com/licensee/licensee) in the form of `project_name: license_file_url`
 * `permissions` - Bulleted list of permission rules
 * `conditions` - Bulleted list of condition rules
 * `limitations` - Bulleted list of limitation rules

_config.yml

@@ -30,8 +30,7 @@ exclude:
   - README.md
   - script
   - vendor/bundle
-  - test
-  - tests
+  - spec
   - assets/vendor/selectivizr/tests
   - assets/vendor/clipboard/test
   - assets/vendor/*/README.*

_includes/footer.html

@@ -34,16 +34,5 @@
     </script>
     <script src="/assets/js/app.js"></script>
     {% endif %}
-
-    <script>
-      !function(L,I,C,e,N,S,E){L.GoogleAnalyticsObject=N,L[N]=L[N]||function(){
-      (L[N].q=L[N].q||[]).push(arguments)},L[N].l=+new Date,S=I.createElement(C),
-      E=I.getElementsByTagName(C)[0],S.src=e,E.parentNode.insertBefore(S,E)
-      }(window,document,"script","//www.google-analytics.com/analytics.js","ga");
-
-      ga('create', 'UA-3769691-24', 'choosealicense.com');
-      ga('send', 'pageview');
-    </script>
-
   </body>
 </html>

_includes/sidebar.html

@@ -4,7 +4,7 @@
   {% unless page.spdx-id == 'LGPL-3.0' %}
   <h3 id="suggest-this-license">Suggest this license</h3>
   <div class="repository-suggestion">
-    <p>Make a pull request to suggest this license for a project that is <a href="/no-permission/">not licensed</a>. Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project's <a href="/community/">community</a>, and keep your communication with project maintainers friendly.</p>
+    <p>Make a pull request to suggest this license for a project that is <a href="/no-permission/">not licensed</a>. Please be polite: see if a license has already been suggested, try to suggest a license fitting for the project’s <a href="/community/">community</a>, and keep your communication with project maintainers friendly.</p>
     <div class="input-wrapper">
       <input type="text" data-license-id="{{ page.spdx-id }}" placeholder="Enter GitHub repository URL" id="repository-url" title="status" />
       <div class="status-indicator"></div>
@@ -26,9 +26,11 @@
     {% endif %}
     {% assign xgpl = false %}
     {% if page.spdx-id contains 'GPL' %}{% assign xgpl = true %}{% endif %}
-    <p id="package-metadata">Add <strong><code>{{ page.spdx-id }}{% if xgpl %}-or-later{% endif %}</code></strong>{% if xgpl %} (or <strong><code>{{ page.spdx-id }}-only</code></strong> to disallow future versions){% endif %} to your project's package description, if applicable (e.g., <a href="https://docs.npmjs.com/files/package.json#license">Node.js</a>, <a href="https://guides.rubygems.org/specification-reference/#license=">Ruby</a>, and <a href="https://doc.rust-lang.org/cargo/reference/manifest.html#package-metadata">Rust</a>). This will ensure the license is displayed in package directories.</p>
+    {% assign ofl = false %}
+    {% if page.spdx-id contains 'OFL-1' %}{% assign ofl = true %}{% endif %}
+    <p id="package-metadata">Add <strong><code>{{ page.spdx-id }}{% if xgpl %}-or-later{% endif %}{% if ofl %}-no-RFN{% endif %}</code></strong>{% if xgpl %} (or <strong><code>{{ page.spdx-id }}-only</code></strong> to disallow future versions){% endif %}{% if ofl %} (or <strong><code>{{ page.spdx-id }}-RFN</code></strong> if a Reserved Font Name is specified after the copyright statement){% endif %} to your project’s package description, if applicable (e.g., <a href="https://docs.npmjs.com/files/package.json#license">Node.js</a>, <a href="https://guides.rubygems.org/specification-reference/#license=">Ruby</a>, and <a href="https://doc.rust-lang.org/cargo/reference/manifest.html#package-metadata">Rust</a>). This will ensure the license is displayed in package directories.</p>
     {% if page.spdx-id contains 'GPL-2' %}
-    <p id="gplcc">If you would like your project to adopt the GPL-3.0's cure provision, add the <a href="https://github.com/gplcc/gplcc/blob/master/Project/COMMITMENT">text</a> of the <a href="https://gplcc.github.io/gplcc/">GPL Cooperation Commitment</a> to a file named <code>COMMITMENT</code> in the same directory as your {{ page.spdx-id }} license file.</p>
+    <p id="gplcc">If you would like your project to adopt the GPL-3.0’s cure provision, add the <a href="https://github.com/gplcc/gplcc/blob/master/Project/COMMITMENT">text</a> of the <a href="https://gplcc.github.io/gplcc/">GPL Cooperation Commitment</a> to a file named <code>COMMITMENT</code> in the same directory as your {{ page.spdx-id }} license file.</p>
     {% endif %}
     </div>
   </div>
@@ -42,12 +44,10 @@
 
   {% if page.using %}
   <div class="projects-with-license">
-    <h3>Who's using this license?</h3>
+    <h3>Who’s using this license?</h3>
     <ul>
       {% for using in page.using %}
-        {% for hash in using %}
-          <li><a href="{{ hash[1] }}" target="_blank">{{ hash[0] }}</a></li>
-        {% endfor %}
+        <li><a href="{{ using[1] }}" target="_blank">{{ using[0] }}</a></li>
       {% endfor %}
     </ul>
   </div>

_includes/using-sentence.html

@@ -8,9 +8,7 @@
       {% if last and using.size > 1 %}
         and
       {% endif %}
-      {% for hash in used %}
-        <a href="{{ hash[1] }}">{{ hash[0] }}</a>{% if last == false %},{% endif %}
-      {% endfor %}
+      <a href="{{ used[1] }}">{{ used[0] }}</a>{% if last == false %},{% endif %}
     {% endfor %}
     use{% if using.size == 1 %}s{% endif %} the {% if license.nickname %}{{ license.nickname }}{% else %}{{ license.title }}{% endif %}.
   {% endif %}

_licenses/0bsd.txt

@@ -7,9 +7,9 @@ description: The BSD Zero Clause license goes further than the BSD 2-Clause lice
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.  Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. You may take the additional step of removing the copyright notice.
 
 using:
-  - PickMeUp: https://github.com/nazar-pc/PickMeUp/blob/master/copying.md
-  - smoltcp: https://github.com/m-labs/smoltcp/blob/master/LICENSE-0BSD.txt
-  - Toybox: https://github.com/landley/toybox/blob/master/LICENSE
+  PickMeUp: https://github.com/nazar-pc/PickMeUp/blob/master/copying.md
+  smoltcp: https://github.com/m-labs/smoltcp/blob/master/LICENSE-0BSD.txt
+  Toybox: https://github.com/landley/toybox/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/apache-2.0.txt

@@ -12,9 +12,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: The Apache Foundation recommends taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text.
 
 using:
-  - Kubernetes: https://github.com/kubernetes/kubernetes/blob/master/LICENSE
-  - PDF.js: https://github.com/mozilla/pdf.js/blob/master/LICENSE
-  - Swift: https://github.com/apple/swift/blob/master/LICENSE.txt
+  Kubernetes: https://github.com/kubernetes/kubernetes/blob/master/LICENSE
+  PDF.js: https://github.com/mozilla/pdf.js/blob/master/LICENSE
+  Swift: https://github.com/apple/swift/blob/main/LICENSE.txt
 
 permissions:
   - commercial-use

_licenses/bsd-2-clause.txt

@@ -9,9 +9,9 @@ description: A permissive license that comes in two variants, the <a href="/lice
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
 
 using:
-  - go-redis: https://github.com/go-redis/redis/blob/master/LICENSE
-  - Homebrew: https://github.com/Homebrew/brew/blob/master/LICENSE.txt
-  - Pony: https://github.com/ponylang/ponyc/blob/master/LICENSE
+  go-redis: https://github.com/go-redis/redis/blob/master/LICENSE
+  Homebrew: https://github.com/Homebrew/brew/blob/master/LICENSE.txt
+  Pony: https://github.com/ponylang/ponyc/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/bsd-3-clause.txt

@@ -8,9 +8,9 @@ description: A permissive license similar to the <a href="/licenses/bsd-2-clause
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
 
 using:
-  - d3: https://github.com/d3/d3/blob/master/LICENSE
-  - LevelDB: https://github.com/google/leveldb/blob/master/LICENSE
-  - Quill: https://github.com/quilljs/quill/blob/develop/LICENSE
+  d3: https://github.com/d3/d3/blob/master/LICENSE
+  LevelDB: https://github.com/google/leveldb/blob/master/LICENSE
+  Quill: https://github.com/quilljs/quill/blob/develop/LICENSE
 
 permissions:
   - commercial-use

_licenses/bsd-4-clause.txt

@@ -7,9 +7,9 @@ description: A permissive license similar to the <a href="/licenses/bsd-3-clause
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work.
 
 using:
-  - Choco-solver: https://github.com/chocoteam/choco-solver/blob/master/LICENSE
-  - PMSPAUR-public: https://github.com/ArthurGodet/PMSPAUR-public/blob/master/LICENSE
-  - Switchblade: https://github.com/SwitchbladeBot/switchblade/blob/dev/LICENSE
+  Choco-solver: https://github.com/chocoteam/choco-solver/blob/master/LICENSE
+  PMSPAUR-public: https://github.com/ArthurGodet/PMSPAUR-public/blob/master/LICENSE
+  Switchblade: https://github.com/SwitchbladeBot/switchblade/blob/dev/LICENSE
 
 permissions:
   - commercial-use

_licenses/bsl-1.0.txt

@@ -10,9 +10,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: Boost recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the [Boost Software License FAQ](https://www.boost.org/users/license.html#FAQ).
 
 using:
-  - Boost: https://github.com/boostorg/boost/blob/master/LICENSE_1_0.txt
-  - Catch2: https://github.com/catchorg/Catch2/blob/master/LICENSE.txt
-  - DMD: https://github.com/dlang/dmd/blob/master/LICENSE.txt
+  Boost: https://github.com/boostorg/boost/blob/master/LICENSE_1_0.txt
+  Catch2: https://github.com/catchorg/Catch2/blob/devel/LICENSE.txt
+  DMD: https://github.com/dlang/dmd/blob/master/LICENSE.txt
 
 permissions:
   - commercial-use

_licenses/cc-by-4.0.txt

@@ -7,9 +7,9 @@ description: Permits almost any use subject to providing credit and license noti
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to solely supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by/4.0/'>canonical URL for the license</a>.
 
 using:
-  - caniuse: https://github.com/Fyrd/caniuse/blob/master/LICENSE
-  - WHATWG HTML standard: https://github.com/whatwg/html/blob/master/LICENSE
-  - Kubernetes documentation: https://github.com/kubernetes/website/blob/master/LICENSE
+  caniuse: https://github.com/Fyrd/caniuse/blob/master/LICENSE
+  WHATWG HTML standard: https://github.com/whatwg/html/blob/master/LICENSE
+  Kubernetes documentation: https://github.com/kubernetes/website/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/cc-by-sa-4.0.txt

@@ -7,9 +7,9 @@ description: Similar to <a href='/licenses/cc-by-4.0/'>CC-BY-4.0</a> but require
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. It is also acceptable to solely supply a link to a copy of the license, usually to the <a href='https://creativecommons.org/licenses/by-sa/4.0/'>canonical URL for the license</a>.
 
 using:
-  - Flight rules for Git: https://github.com/k88hudson/git-flight-rules/blob/master/LICENSE
-  - Material Design Iconic Font: https://github.com/zavoloklom/material-design-iconic-font/blob/master/License.md
-  - OWASP MSTG: https://github.com/OWASP/owasp-mstg/blob/master/License.md
+  Flight rules for Git: https://github.com/k88hudson/git-flight-rules/blob/master/LICENSE
+  Material Design Iconic Font: https://github.com/zavoloklom/material-design-iconic-font/blob/master/License.md
+  OWASP MSTG: https://github.com/OWASP/owasp-mstg/blob/master/License.md
 
 permissions:
   - commercial-use

_licenses/cc0-1.0.txt

@@ -11,9 +11,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: Creative Commons recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be <a href="https://wiki.creativecommons.org/wiki/CC0_FAQ#May_I_apply_CC0_to_computer_software.3F_If_so.2C_is_there_a_recommended_implementation.3F">found on their website</a>.
 
 using:
-  - Awesome: https://github.com/sindresorhus/awesome/blob/main/license
-  - Shields.io: https://github.com/badges/shields/blob/master/LICENSE
-  - psdash: https://github.com/Jahaja/psdash/blob/master/LICENSE
+  Awesome: https://github.com/sindresorhus/awesome/blob/main/license
+  Shields.io: https://github.com/badges/shields/blob/master/LICENSE
+  psdash: https://github.com/Jahaja/psdash/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/cecill-2.1.txt

@@ -7,9 +7,9 @@ description: Strong copyleft license made by three French public research organi
 how: Create a text file (typically named LICENSE or LICENCE) in the root of your source code and copy the text of the license into the file.
 
 using:
-  - BMC-Tools: https://github.com/ANSSI-FR/bmc-tools/blob/master/LICENCE.txt
-  - Taxe foncière: https://github.com/etalab/taxe-fonciere/blob/master/LICENSE
-  - VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-fr.txt
+  BMC-Tools: https://github.com/ANSSI-FR/bmc-tools/blob/master/LICENCE.txt
+  Taxe foncière: https://github.com/etalab/taxe-fonciere/blob/master/LICENSE
+  VITAM: https://github.com/ProgrammeVitam/vitam/blob/master_0.15.x/Licence_CeCILL_V2.1-fr.txt
 
 permissions:
   - commercial-use

_licenses/ecl-2.0.txt

@@ -9,9 +9,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: The Apereo Foundation recommends taking the additional step of adding a boilerplate notice to the header of each source file. You can find the notice in the appendix at the very end of the license text.
 
 using:
-  - Sakai: https://github.com/sakaiproject/sakai/blob/master/LICENSE
-  - OAE: https://github.com/oaeproject/Hilary/blob/master/LICENSE
-  - Opencast: https://github.com/opencast/opencast/blob/develop/LICENSE
+  Sakai: https://github.com/sakaiproject/sakai/blob/master/LICENSE
+  OAE: https://github.com/oaeproject/Hilary/blob/master/LICENSE
+  Opencast: https://github.com/opencast/opencast/blob/develop/LICENSE
 
 permissions:
   - commercial-use

_licenses/epl-1.0.txt

@@ -7,9 +7,9 @@ description: This commercially-friendly copyleft license provides the ability to
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
 
 using:
-  - Eclipse hawkBit: https://github.com/eclipse/hawkbit/blob/master/LICENSE
-  - JUnit: https://github.com/junit-team/junit4/blob/main/LICENSE-junit.txt
-  - Quil: https://github.com/quil/quil/blob/master/LICENSE
+  Eclipse hawkBit: https://github.com/eclipse/hawkbit/blob/master/LICENSE
+  JUnit: https://github.com/junit-team/junit4/blob/main/LICENSE-junit.txt
+  Quil: https://github.com/quil/quil/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/epl-2.0.txt

@@ -9,9 +9,9 @@ description: This commercially-friendly copyleft license provides the ability to
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
 
 using:
-  - Eclipse SmartHome: https://github.com/eclipse/smarthome/blob/master/LICENSE
-  - openHAB: https://github.com/openhab/openhab-distro/blob/master/LICENSE
-  - SUMO: https://github.com/eclipse/sumo/blob/master/LICENSE
+  Eclipse SmartHome: https://github.com/eclipse/smarthome/blob/master/LICENSE
+  openHAB: https://github.com/openhab/openhab-distro/blob/master/LICENSE
+  SUMO: https://github.com/eclipse/sumo/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/eupl-1.2.txt

@@ -2,14 +2,14 @@
 title: European Union Public License 1.2
 spdx-id: EUPL-1.2
 
-description: The European Union Public Licence (EUPL) is a copyleft free/open source software license created on the initiative of and approved by the European Commission in 22 official languages of the European Union.
+description: The European Union Public Licence (EUPL) is a copyleft free/open source software license created on the initiative of and approved by the European Commission in <a href="https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12">23 official languages</a> of the European Union.
 
 how: Indicate “Licensed under the EUPL” following the copyright notice of your source code, for example in a README file or directly in a source code file as a comment.
 
 using:
-  - AethysRotation: https://github.com/SimCMinMax/AethysRotation/blob/master/LICENSE
-  - WildDuck: https://github.com/nodemailer/wildduck/blob/master/LICENSE
-  - ZoneMTA: https://github.com/zone-eu/zone-mta/blob/master/LICENSE
+  HeroRotation: https://github.com/herotc/hero-rotation/blob/shadowlands/LICENSE
+  WildDuck: https://github.com/nodemailer/wildduck/blob/master/LICENSE
+  ZoneMTA: https://github.com/zone-eu/zone-mta/blob/master/LICENSE
 
 permissions:
   - commercial-use
@@ -32,10 +32,8 @@ limitations:
 
 ---
 
-European Union Public Licence
-V. 1.2
-
-EUPL © the European Union 2007, 2016
+                      EUROPEAN UNION PUBLIC LICENCE v. 1.2
+                      EUPL © the European Union 2007, 2016
 
 This European Union Public Licence (the ‘EUPL’) applies to the Work (as
 defined below) which is provided under the terms of this Licence. Any use of
@@ -44,35 +42,47 @@ extent such use is covered by a right of the copyright holder of the Work).
 
 The Work is provided under the terms of this Licence when the Licensor (as
 defined below) has placed the following notice immediately following the
-copyright notice for the Work: “Licensed under the EUPL”, or has expressed by
-any other means his willingness to license under the EUPL.
+copyright notice for the Work:
+
+        Licensed under the EUPL
+
+or has expressed by any other means his willingness to license under the EUPL.
 
 1. Definitions
 
 In this Licence, the following terms have the following meaning:
-— ‘The Licence’: this Licence.
-— ‘The Original Work’: the work or software distributed or communicated by the
-  ‘Licensor under this Licence, available as Source Code and also as
-  ‘Executable Code as the case may be.
-— ‘Derivative Works’: the works or software that could be created by the
-  ‘Licensee, based upon the Original Work or modifications thereof. This
-  ‘Licence does not define the extent of modification or dependence on the
-  ‘Original Work required in order to classify a work as a Derivative Work;
-  ‘this extent is determined by copyright law applicable in the country
-  ‘mentioned in Article 15.
-— ‘The Work’: the Original Work or its Derivative Works.
-— ‘The Source Code’: the human-readable form of the Work which is the most
+
+- ‘The Licence’: this Licence.
+
+- ‘The Original Work’: the work or software distributed or communicated by the
+  Licensor under this Licence, available as Source Code and also as Executable
+  Code as the case may be.
+
+- ‘Derivative Works’: the works or software that could be created by the
+  Licensee, based upon the Original Work or modifications thereof. This
+  Licence does not define the extent of modification or dependence on the
+  Original Work required in order to classify a work as a Derivative Work;
+  this extent is determined by copyright law applicable in the country
+  mentioned in Article 15.
+
+- ‘The Work’: the Original Work or its Derivative Works.
+
+- ‘The Source Code’: the human-readable form of the Work which is the most
   convenient for people to study and modify.
 
-— ‘The Executable Code’: any code which has generally been compiled and which
+- ‘The Executable Code’: any code which has generally been compiled and which
   is meant to be interpreted by a computer as a program.
-— ‘The Licensor’: the natural or legal person that distributes or communicates
+
+- ‘The Licensor’: the natural or legal person that distributes or communicates
   the Work under the Licence.
-— ‘Contributor(s)’: any natural or legal person who modifies the Work under
+
+- ‘Contributor(s)’: any natural or legal person who modifies the Work under
   the Licence, or otherwise contributes to the creation of a Derivative Work.
-— ‘The Licensee’ or ‘You’: any natural or legal person who makes any usage of
+
+- ‘The Licensee’ or ‘You’: any natural or legal person who makes any usage of
   the Work under the terms of the Licence.
-— ‘Distribution’ or ‘Communication’: any act of selling, giving, lending,
+
+- ‘Distribution’ or ‘Communication’: any act of selling, giving, lending,
   renting, distributing, communicating, transmitting, or otherwise making
   available, online or offline, copies of the Work or providing access to its
   essential functionalities at the disposal of any other natural or legal
@@ -84,15 +94,15 @@ The Licensor hereby grants You a worldwide, royalty-free, non-exclusive,
 sublicensable licence to do the following, for the duration of copyright
 vested in the Original Work:
 
-— use the Work in any circumstance and for all usage,
-— reproduce the Work,
-— modify the Work, and make Derivative Works based upon the Work,
-— communicate to the public, including the right to make available or display
+- use the Work in any circumstance and for all usage,
+- reproduce the Work,
+- modify the Work, and make Derivative Works based upon the Work,
+- communicate to the public, including the right to make available or display
   the Work or copies thereof to the public and perform publicly, as the case
   may be, the Work,
-— distribute the Work or copies thereof,
-— lend and rent the Work or copies thereof,
-— sublicense rights in the Work or copies thereof.
+- distribute the Work or copies thereof,
+- lend and rent the Work or copies thereof,
+- sublicense rights in the Work or copies thereof.
 
 Those rights can be exercised on any media, supports and formats, whether now
 known or later invented, as far as the applicable law permits so.
@@ -238,10 +248,11 @@ accessible, concluded, stored and reproduced by the Licensee.
 12. Termination of the Licence
 
 The Licence and the rights granted hereunder will terminate automatically upon
-any breach by the Licensee of the terms of the Licence. Such a termination
-will not terminate the licences of any person who has received the Work from
-the Licensee under the Licence, provided such persons remain in full
-compliance with the Licence.
+any breach by the Licensee of the terms of the Licence.
+
+Such a termination will not terminate the licences of any person who has
+received the Work from the Licensee under the Licence, provided such persons
+remain in full compliance with the Licence.
 
 13. Miscellaneous
 
@@ -266,12 +277,14 @@ their choice.
 14. Jurisdiction
 
 Without prejudice to specific agreement between parties,
-— any litigation resulting from the interpretation of this License, arising
+
+- any litigation resulting from the interpretation of this License, arising
   between the European Union institutions, bodies, offices or agencies, as a
   Licensor, and any Licensee, will be subject to the jurisdiction of the Court
   of Justice of the European Union, as laid down in article 272 of the Treaty
   on the Functioning of the European Union,
-— any litigation arising between other parties and resulting from the
+
+- any litigation arising between other parties and resulting from the
   interpretation of this License, will be subject to the exclusive
   jurisdiction of the competent court where the Licensor resides or conducts
   its primary business.
@@ -279,30 +292,34 @@ Without prejudice to specific agreement between parties,
 15. Applicable Law
 
 Without prejudice to specific agreement between parties,
-— this Licence shall be governed by the law of the European Union Member State
+
+- this Licence shall be governed by the law of the European Union Member State
   where the Licensor has his seat, resides or has his registered office,
-— this licence shall be governed by Belgian law if the Licensor has no seat,
+
+- this licence shall be governed by Belgian law if the Licensor has no seat,
   residence or registered office inside a European Union Member State.
 
 Appendix
 
 ‘Compatible Licences’ according to Article 5 EUPL are:
-— GNU General Public License (GPL) v. 2, v. 3
-— GNU Affero General Public License (AGPL) v. 3
-— Open Software License (OSL) v. 2.1, v. 3.0
-— Eclipse Public License (EPL) v. 1.0
-— CeCILL v. 2.0, v. 2.1
-— Mozilla Public Licence (MPL) v. 2
-— GNU Lesser General Public Licence (LGPL) v. 2.1, v. 3
-— Creative Commons Attribution-ShareAlike v. 3.0 Unported (CC BY-SA 3.0) for
-  works other than software
-— European Union Public Licence (EUPL) v. 1.1, v. 1.2
-— Québec Free and Open-Source Licence — Reciprocity (LiLiQ-R) or
-  Strong Reciprocity (LiLiQ-R+)
 
-— The European Commission may update this Appendix to later versions of the
-  above licences without producing a new version of the EUPL, as long as they
-  provide the rights granted in Article 2 of this Licence and protect the
-  covered Source Code from exclusive appropriation.
-— All other changes or additions to this Appendix require the production of a
-  new EUPL version.
+- GNU General Public License (GPL) v. 2, v. 3
+- GNU Affero General Public License (AGPL) v. 3
+- Open Software License (OSL) v. 2.1, v. 3.0
+- Eclipse Public License (EPL) v. 1.0
+- CeCILL v. 2.0, v. 2.1
+- Mozilla Public Licence (MPL) v. 2
+- GNU Lesser General Public Licence (LGPL) v. 2.1, v. 3
+- Creative Commons Attribution-ShareAlike v. 3.0 Unported (CC BY-SA 3.0) for
+  works other than software
+- European Union Public Licence (EUPL) v. 1.1, v. 1.2
+- Québec Free and Open-Source Licence — Reciprocity (LiLiQ-R) or Strong
+  Reciprocity (LiLiQ-R+).
+
+The European Commission may update this Appendix to later versions of the
+above licences without producing a new version of the EUPL, as long as they
+provide the rights granted in Article 2 of this Licence and protect the
+covered Source Code from exclusive appropriation.
+
+All other changes or additions to this Appendix require the production of a
+new EUPL version.

_licenses/gpl-2.0.txt

@@ -12,9 +12,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license.
 
 using:
-  - AliSQL: https://github.com/alibaba/AliSQL/blob/master/COPYING
-  - Discourse: https://github.com/discourse/discourse/blob/master/LICENSE.txt
-  - Joomla!: https://github.com/joomla/joomla-cms/blob/staging/LICENSE.txt
+  AliSQL: https://github.com/alibaba/AliSQL/blob/master/COPYING
+  Discourse: https://github.com/discourse/discourse/blob/master/LICENSE.txt
+  Joomla!: https://github.com/joomla/joomla-cms/blob/staging/LICENSE.txt
 
 permissions:
   - commercial-use

_licenses/gpl-3.0.txt

@@ -13,9 +13,9 @@ how: Create a text file (typically named COPYING, as per GNU conventions) in the
 note: The Free Software Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license.
 
 using:
-  - Ansible: https://github.com/ansible/ansible/blob/devel/COPYING
-  - Bash: https://git.savannah.gnu.org/cgit/bash.git/tree/COPYING
-  - GIMP: https://git.gnome.org/browse/gimp/tree/COPYING
+  Ansible: https://github.com/ansible/ansible/blob/devel/COPYING
+  Bash: https://git.savannah.gnu.org/cgit/bash.git/tree/COPYING
+  GIMP: https://git.gnome.org/browse/gimp/tree/COPYING
 
 permissions:
   - commercial-use

_licenses/isc.txt

@@ -7,9 +7,9 @@ description: A permissive license lets people do anything with your code with pr
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
 
 using:
-  - Starship: https://github.com/starship/starship/blob/master/LICENSE
-  - Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE
-  - OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/develop/LICENSE.md
+  Starship: https://github.com/starship/starship/blob/master/LICENSE
+  Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE
+  OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/develop/LICENSE.md
 
 permissions:
   - commercial-use

_licenses/mit.txt

@@ -9,9 +9,9 @@ description: A short and simple permissive license with conditions only requirin
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
 
 using:
-  - Babel: https://github.com/babel/babel/blob/master/LICENSE
-  - .NET Core: https://github.com/dotnet/runtime/blob/master/LICENSE.TXT
-  - Rails: https://github.com/rails/rails/blob/master/MIT-LICENSE
+  Babel: https://github.com/babel/babel/blob/master/LICENSE
+  .NET Core: https://github.com/dotnet/runtime/blob/master/LICENSE.TXT
+  Rails: https://github.com/rails/rails/blob/master/MIT-LICENSE
 
 permissions:
   - commercial-use

_licenses/mpl-2.0.txt

@@ -11,9 +11,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: The Mozilla Foundation recommends taking the additional step of adding a boilerplate notice to the top of each file. The boilerplate can be found at the end of the license (Exhibit A).
 
 using:
-  - Servo: https://github.com/servo/servo/blob/master/LICENSE
-  - Syncthing: https://github.com/syncthing/syncthing/blob/main/LICENSE
-  - TimelineJS3: https://github.com/NUKnightLab/TimelineJS3/blob/master/LICENSE
+  Servo: https://github.com/servo/servo/blob/master/LICENSE
+  Syncthing: https://github.com/syncthing/syncthing/blob/main/LICENSE
+  TimelineJS3: https://github.com/NUKnightLab/TimelineJS3/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/ncsa.txt

@@ -8,9 +8,9 @@ description: The University of Illinois/NCSA Open Source License, or UIUC licens
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders. Replace [project] with the project organization, if any, that sponsors this work.
 
 using:
- - ROCR-Runtime: https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/master/LICENSE.txt
- - RLTK: https://github.com/chriswailes/RLTK/blob/master/LICENSE
- - ToaruOS: https://github.com/klange/toaruos/blob/master/LICENSE
+  ROCR-Runtime: https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/master/LICENSE.txt
+  RLTK: https://github.com/chriswailes/RLTK/blob/master/LICENSE
+  ToaruOS: https://github.com/klange/toaruos/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/odbl-1.0.txt

@@ -8,9 +8,9 @@ description: The Open Database License (ODbL) is a license agreement intended to
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file.
 
 using:
-  - World Countries: https://github.com/mledoze/countries/blob/master/LICENSE
-  - OpenFlights: https://github.com/jpatokal/openflights/blob/master/data/LICENSE
-  - Public Zone Database: https://github.com/zonedb/zonedb/blob/master/LICENSE.md
+  World Countries: https://github.com/mledoze/countries/blob/master/LICENSE
+  OpenFlights: https://github.com/jpatokal/openflights/blob/master/data/LICENSE
+  Public Zone Database: https://github.com/zonedb/zonedb/blob/main/LICENSE.md
 
 permissions:
   - commercial-use

_licenses/ofl-1.1.txt

@@ -10,9 +10,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: This license doesn't require source provision, but recommends it. All files derived from OFL files must remain licensed under the OFL.
 
 using:
-  - FiraCode: https://github.com/tonsky/FiraCode/blob/master/LICENSE
-  - Noto fonts: https://github.com/googlefonts/noto-fonts/blob/master/LICENSE
-  - Fantasque Sans Mono: https://github.com/belluzj/fantasque-sans/blob/master/LICENSE.txt
+  FiraCode: https://github.com/tonsky/FiraCode/blob/master/LICENSE
+  Noto fonts: https://github.com/googlefonts/noto-fonts/blob/master/LICENSE
+  Fantasque Sans Mono: https://github.com/belluzj/fantasque-sans/blob/master/LICENSE.txt
 
 permissions:
   - private-use

_licenses/osl-3.0.txt

@@ -9,9 +9,9 @@ how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of
 note: OSL 3.0's author has <a href="https://rosenlaw.com/OSL3.0-explained.htm">provided an explanation</a> behind the creation of the license.
 
 using:
-  - appserver.io: https://github.com/appserver-io/appserver/blob/master/LICENSE.txt
-  - JsonMapper: https://github.com/cweiske/jsonmapper/blob/master/LICENSE
-  - Restyaboard: https://github.com/RestyaPlatform/board/blob/master/LICENSE.txt
+  appserver.io: https://github.com/appserver-io/appserver/blob/master/LICENSE.txt
+  JsonMapper: https://github.com/cweiske/jsonmapper/blob/master/LICENSE
+  Restyaboard: https://github.com/RestyaPlatform/board/blob/master/LICENSE.txt
 
 permissions:
   - commercial-use

_licenses/postgresql.txt

@@ -7,9 +7,9 @@ description: A very short, BSD-style license, used specifically for PostgreSQL.
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
 
 using:
-  - pgBadger: https://github.com/darold/pgbadger/blob/master/LICENSE
-  - pgAdmin: https://github.com/postgres/pgadmin4/blob/master/LICENSE
-  - .NET Access to PostgreSQL: https://github.com/npgsql/npgsql/blob/dev/LICENSE
+  pgBadger: https://github.com/darold/pgbadger/blob/master/LICENSE
+  pgAdmin: https://github.com/postgres/pgadmin4/blob/master/LICENSE
+  .NET Access to PostgreSQL: https://github.com/npgsql/npgsql/blob/main/LICENSE
 
 permissions:
   - commercial-use

_licenses/unlicense.txt

@@ -8,9 +8,9 @@ description: A license with no conditions whatsoever which dedicates works to th
 how: Create a text file (typically named UNLICENSE or UNLICENSE.txt) in the root of your source code and copy the text of the license disclaimer into the file.
 
 using:
-  - youtube-dl: https://github.com/rg3/youtube-dl/blob/master/LICENSE
-  - kakoune: https://github.com/mawww/kakoune/blob/master/UNLICENSE
-  - RDF.rb: https://github.com/ruby-rdf/rdf/blob/master/UNLICENSE
+  scoop: https://github.com/lukesampson/scoop/blob/master/LICENSE
+  kakoune: https://github.com/mawww/kakoune/blob/master/UNLICENSE
+  RDF.rb: https://github.com/ruby-rdf/rdf/blob/master/UNLICENSE
 
 permissions:
   - private-use

_licenses/upl-1.0.txt

@@ -9,9 +9,9 @@ how: Insert the license or a link to it along with a copyright notice into your
 note: It is recommended to add a link to the license and copyright notice at the top of each source file, example text can be found at https://oss.oracle.com/licenses/upl/.
 
 using:
-  - Oracle Product Images for Docker: https://github.com/oracle/docker-images/blob/master/LICENSE
-  - Skater: https://github.com/oracle/Skater/blob/master/LICENSE
-  - Soufflé: https://github.com/souffle-lang/souffle/blob/master/LICENSE
+  Oracle Product Images for Docker: https://github.com/oracle/docker-images/blob/master/LICENSE
+  Skater: https://github.com/oracle/Skater/blob/master/LICENSE
+  Soufflé: https://github.com/souffle-lang/souffle/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/vim.txt

@@ -7,9 +7,9 @@ description: There are no restrictions on using or distributing an unmodified co
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [project] with the project name.
 
 using:
-  - Vim: https://github.com/vim/vim/blob/master/LICENSE
-  - Pathogen: https://github.com/tpope/vim-pathogen/blob/master/LICENSE
-  - vim-license-gen: https://github.com/othree/vim-license/blob/master/LICENSE
+  Vim: https://github.com/vim/vim/blob/master/LICENSE
+  Pathogen: https://github.com/tpope/vim-pathogen/blob/master/LICENSE
+  vim-license-gen: https://github.com/othree/vim-license/blob/master/LICENSE
 
 permissions:
   - commercial-use

_licenses/zlib.txt

@@ -7,9 +7,9 @@ description: A short permissive license, compatible with GPL. Requires altered s
 how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] with the name (or names) of the copyright holders.
 
 using:
-  - GLFW: https://github.com/glfw/glfw/blob/master/LICENSE.md
-  - Portainer: https://github.com/portainer/portainer/blob/develop/LICENSE
-  - TinyXML-2: https://github.com/leethomason/tinyxml2/blob/master/LICENSE.txt
+  GLFW: https://github.com/glfw/glfw/blob/master/LICENSE.md
+  Portainer: https://github.com/portainer/portainer/blob/develop/LICENSE
+  TinyXML-2: https://github.com/leethomason/tinyxml2/blob/master/LICENSE.txt
 
 permissions:
   - commercial-use

licenses.html

@@ -6,7 +6,7 @@ title: Licenses
 ---
 
 <p>Open source licenses grant permission for anybody to use, modify, and share licensed software for any purpose, subject to conditions preserving the provenance and openness of the software. The following licenses are sorted by the number of conditions, from most (GNU AGPLv3) to none (Unlicense). Notice that the popular licenses featured on the <a href="/">home page</a> (GNU GPLv3 and MIT) fall within this spectrum.</p>
-<p style="font-size:small; margin-bottom: 40px">If you're looking for a reference table of every license on choosealicense.com, see the <a href="/appendix">appendix</a>.</p>
+<p style="font-size:small; margin-bottom: 40px">If you’re looking for a reference table of every license on choosealicense.com, see the <a href="/appendix">appendix</a>.</p>
 
 {% include license-overview.html license-id="agpl-3.0" %}
 {% include license-overview.html license-id="gpl-3.0" %}
@@ -17,4 +17,4 @@ title: Licenses
 {% include license-overview.html license-id="bsl-1.0" %}
 {% include license-overview.html license-id="unlicense" %}
 
-The above licenses represent the entire spectrum of open source licenses, from highly protective to unconditional. One of these should work for most new open source projects. Many other open source licenses exist, including older versions of and close substitutes for some of the above. See the resources listed on our <a href="/about/">about page</a> if you'd like to read more.
+The above licenses represent the entire spectrum of open source licenses, from highly protective to unconditional. One of these should work for most new open source projects. Many other open source licenses exist, including older versions of and close substitutes for some of the above. See the resources listed on our <a href="/about/">about page</a> if you’d like to read more.

non-software.md

@@ -16,8 +16,8 @@ Any open source software license or open license for media (see [above](#data-me
 
 ### Fonts
 
-The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open but allows them to be freely used in other works.
+The [SIL Open Font License 1.1](/licenses/ofl-1.1/) keeps fonts open, allowing them to be freely used in other works.
 
-### Mixed Projects
+### Mixed projects
 
 If your project contains a mix of software and other material, you can include multiple licenses, as long as you are explicit about which license applies to each part of the project. See [the license notice for this site](https://github.com/github/choosealicense.com#license) as an example.

spec/license_meta_spec.rb

@@ -19,7 +19,7 @@ describe 'license meta' do
         expect(missing).to be_empty
       end
 
-      examples = raw_fields['using'] || []
+      examples = raw_fields['using'] || {}
 
       it 'using contains 3 examples' do
         legacy = [
@@ -42,9 +42,7 @@ describe 'license meta' do
       context 'licensee detects using examples' do
         slug = license['slug']
 
-        examples.each do |example|
-          example_url = example.values[0]
-
+        examples.each_value do |example_url|
           context "the #{example_url} URL" do
             let(:content)  { OpenURI.open_uri(example_url).read }
             let(:detected) { Licensee::ProjectFiles::LicenseFile.new(content, 'LICENSE').license }

spec/license_shown_spec.rb

@@ -2,25 +2,25 @@
 
 require 'spec_helper'
 
-describe 'shown licenses' do
-  # Whitelist of popular licenses that are shown (non-hidden)
-  # Note: most new licenses that are added should be hidden by default
-  SHOWN_LICENSES = %w[
-    agpl-3.0
-    apache-2.0
-    bsd-2-clause
-    bsd-3-clause
-    bsl-1.0
-    cc0-1.0
-    epl-2.0
-    gpl-2.0
-    gpl-3.0
-    lgpl-2.1
-    mit
-    mpl-2.0
-    unlicense
-  ].freeze
+# Popular licenses that are shown (non-hidden)
+# Note: most new licenses that are added should be hidden by default
+SHOWN_LICENSES = %w[
+  agpl-3.0
+  apache-2.0
+  bsd-2-clause
+  bsd-3-clause
+  bsl-1.0
+  cc0-1.0
+  epl-2.0
+  gpl-2.0
+  gpl-3.0
+  lgpl-2.1
+  mit
+  mpl-2.0
+  unlicense
+].freeze
 
+describe 'shown licenses' do
   it 'has the expected number of shown licenses' do
     expect(shown_licenses.count).to eql(13)
     expect(SHOWN_LICENSES.count).to eql(shown_licenses.count)

terms-of-service.md

@@ -27,7 +27,7 @@ The next few sections of these Terms go into greater detail on these disclaimers
 
 ### 4. DISCLAIMER OF WARRANTIES
 
-TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, GITHUB OFFERS THE SITE ON AN AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WEBSITES OR SERVICES, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTIBILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. GITHUB DOES NOT WARRANT THAT THE FUNCTIONS OR CONTENT CONTAINED ON THE WEBSITE OR SERVICES WILL BE ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT GITHUB'S SERVERS ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. GITHUB DOES NOT WARRANT OR MAKE ANY REPRESENTATION REGARDING USE OR THE RESULT OF USE OF THE CONTENT IN TERMS OF ACCURACY, RELIABILITY, OR OTHERWISE.
+TO THE FULLEST EXTENT PERMITTED BY APPLICABLE LAW, GITHUB OFFERS THE SITE ON AN AS-IS AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE WEBSITES OR SERVICES, EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, INCLUDING, WITHOUT LIMITATION, WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. GITHUB DOES NOT WARRANT THAT THE FUNCTIONS OR CONTENT CONTAINED ON THE WEBSITE OR SERVICES WILL BE ERROR-FREE, THAT DEFECTS WILL BE CORRECTED, OR THAT GITHUB'S SERVERS ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. GITHUB DOES NOT WARRANT OR MAKE ANY REPRESENTATION REGARDING USE OR THE RESULT OF USE OF THE CONTENT IN TERMS OF ACCURACY, RELIABILITY, OR OTHERWISE.
 
 ### 5. LIMITATION OF LIABILITY