licensee 9.13.0 → 9.15.0

data/vendor/choosealicense.com/_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

data/vendor/choosealicense.com/_licenses/gpl-3.0.txt

@@ -8,14 +8,14 @@ hidden: false
 
 description: Permissions of this strong copyleft license are conditioned on making available complete source code of licensed works and modifications, which include larger works using a licensed work, under the same license. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights.
 
-how: Create a text file in the root of your source code, typically named COPYING (a GNU convention), LICENSE or LICENSE.txt. Then copy the text of the license into that file.
+how: Create a text file (typically named COPYING, as per GNU conventions) in the root of your source code and copy the text of the license into the file.
 
 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

data/vendor/choosealicense.com/_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:
-  - Helix: https://github.com/tildeio/helix/blob/master/LICENSE
-  - Node.js semver: https://github.com/npm/node-semver/blob/master/LICENSE
-  - OpenStreetMap iD: https://github.com/openstreetmap/iD/blob/master/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

data/vendor/choosealicense.com/_licenses/lgpl-3.0.txt

@@ -3,7 +3,6 @@ title: GNU Lesser General Public License v3.0
 spdx-id: LGPL-3.0
 nickname: GNU LGPLv3
 redirect_from: /licenses/lgpl-v3/
-hidden: false
 
 description: Permissions of this copyleft license are conditioned on making available complete source code of licensed works and modifications under the same license or the GNU GPLv3. Copyright and license notices must be preserved. Contributors provide an express grant of patent rights. However, a larger work using the licensed work through interfaces provided by the licensed work may be distributed under different terms and without source code for the larger work.
 

data/vendor/choosealicense.com/_licenses/lppl-1.3c.txt

@@ -4,7 +4,7 @@ spdx-id: LPPL-1.3c
 
 description: The LaTeX Project Public License (LPPL) is the primary license under which the LaTeX kernel and the base LaTeX packages are distributed.
 
-how: To use this license, place in each of the components of your work both an explicit copyright notice including your name and the year the work was authored and/or last substantially modified. Include also a statement that the distribution and/or modification of that component is constrained by the conditions in this license.
+how: Place in each of the components of your work both an explicit copyright notice including your name, and the year the work was authored and/or last substantially modified. Include also a statement that the distribution and/or modification of that component is constrained by the conditions in this license.
 
 note: An example boilerplate and more information about how to use the license can be found at the end of the license.
 

data/vendor/choosealicense.com/_licenses/mit-0.txt

@@ -0,0 +1,45 @@
+---
+title: MIT No Attribution
+spdx-id: MIT-0
+
+description: A short and simple permissive license with no conditions, not even requiring preservation of copyright and license notices. Licensed works, modifications, and larger works may be distributed under different terms and without source code.
+
+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:
+  rssfs: https://github.com/dertuxmalwieder/rssfs/blob/master/LICENSE
+  SOIL2: https://github.com/SpartanJ/SOIL2/blob/master/LICENSE
+  Units.NET: https://github.com/angularsen/UnitsNet/blob/master/LICENSE
+
+permissions:
+  - commercial-use
+  - modifications
+  - distribution
+  - private-use
+
+conditions: []
+
+limitations:
+  - liability
+  - warranty
+
+---
+
+MIT No Attribution
+
+Copyright [year] [fullname]
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

data/vendor/choosealicense.com/_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/corefx/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

data/vendor/choosealicense.com/_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/master/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

data/vendor/choosealicense.com/_licenses/ncsa.txt

@@ -7,10 +7,10 @@ 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: 
- - LLDB: https://github.com/llvm-mirror/lldb/blob/master/LICENSE.TXT
- - ROCR-Runtime: https://github.com/RadeonOpenCompute/ROCR-Runtime/blob/master/LICENSE.txt
- - RLTK: https://github.com/chriswailes/RLTK/blob/master/LICENSE
+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
 
 permissions:
   - commercial-use
@@ -27,37 +27,37 @@ limitations:
 
 ---
 
-University of Illinois/NCSA Open Source License 
+University of Illinois/NCSA Open Source License
 
-Copyright (c) [year] [fullname]. All rights reserved. 
+Copyright (c) [year] [fullname]. All rights reserved.
 
-Developed by: [project] 
-              [fullname] 
+Developed by: [project]
+              [fullname]
               [projecturl]
-                  
-Permission is hereby granted, free of charge, to any person 
-obtaining a copy of this software and associated documentation files 
-(the "Software"), to deal with the Software without restriction, 
+
+Permission is hereby granted, free of charge, to any person
+obtaining a copy of this software and associated documentation files
+(the "Software"), to deal with the Software without restriction,
 including without limitation the rights to use, copy, modify, merge,
-publish, distribute, sublicense, and/or sell copies of the Software, 
-and to permit persons to whom the Software is furnished to do so, 
+publish, distribute, sublicense, and/or sell copies of the Software,
+and to permit persons to whom the Software is furnished to do so,
 subject to the following conditions:
 
-* Redistributions of source code must retain the above copyright notice, 
+* Redistributions of source code must retain the above copyright notice,
   this list of conditions and the following disclaimers.
 
-* Redistributions in binary form must reproduce the above copyright 
-  notice, this list of conditions and the following disclaimers in the 
+* Redistributions in binary form must reproduce the above copyright
+  notice, this list of conditions and the following disclaimers in the
   documentation and/or other materials provided with the distribution.
 
-* Neither the names of [fullname], [project] nor the names of its 
+* Neither the names of [fullname], [project] nor the names of its
   contributors may be used to endorse or promote products derived from
   this Software without specific prior written permission.
-  
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS 
-OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
-CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
+OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+CONTRIBUTORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS WITH
 THE SOFTWARE.

data/vendor/choosealicense.com/_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

data/vendor/choosealicense.com/_licenses/ofl-1.1.txt

@@ -5,14 +5,14 @@ redirect_from: /licenses/ofl/
 
 description: The Open Font License (OFL) is maintained by SIL International. It attempts to be a compromise between the values of the free software and typeface design communities. It is used for almost all open source font projects, including those by Adobe, Google and Mozilla.
 
-how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your font source and copy the text of the license into the file. Replace [year] with the current year and [fullname] ([email]) with the name and contact email address of each copyright holder. You may take the additional step of appending a Reserved Font Name notice. This option requires anyone making modifications to change the font's name, and is not ideal for web fonts (which all users will modify by changing formats and subsetting for their own needs.)
+how: Create a text file (typically named LICENSE or LICENSE.txt) in the root of your font's source code and copy the text of the license into the file. Replace [year] with the current year and [fullname] ([email]) with the name and contact email address of each copyright holder. You may take the additional step of appending a Reserved Font Name notice. This option requires anyone making modifications to change the font's name, and is not ideal for web fonts (which all users will modify by changing formats and subsetting for their own needs.)
 
 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

data/vendor/choosealicense.com/_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

data/vendor/choosealicense.com/_licenses/postgresql.txt

@@ -2,14 +2,14 @@
 title: PostgreSQL License
 spdx-id: PostgreSQL
 
-description: A very short, BSD-style license, used specifically for PostgreSQL.  
+description: A very short, BSD-style license, used specifically for PostgreSQL.
 
-how: To use it, say that it is The PostgreSQL License, and then substitute the copyright year and name of the copyright holder into the body of the license. Then put the license into a prominent file ("COPYRIGHT", "LICENSE" or "COPYING" are common names for this file) in your software distribution.
+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

data/vendor/choosealicense.com/_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

data/vendor/choosealicense.com/_licenses/upl-1.0.txt

@@ -4,14 +4,14 @@ spdx-id: UPL-1.0
 
 description: A permissive, OSI and FSF approved, GPL compatible license, expressly allowing attribution with just a copyright notice and a short form link rather than the full text of the license.  Includes an express grant of patent rights.  Licensed works and modifications may be distributed under different terms and without source code, and the patent grant may also optionally be expanded to larger works to permit use as a contributor license agreement.
 
-how: Insert the license or a link to it along with a copyright notice into your source file(s), and/or create a text file (typically named LICENSE or LICENSE.txt) in the root of your source code and copy the text of the license and your copyright notice into the file.
+how: Insert the license or a link to it along with a copyright notice into your source file(s), and/or 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, replacing [year] with the current year and [fullname] with the name (or names) of the copyright holders.
 
 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 Boxes for Vagrant: https://github.com/oracle/vagrant-boxes/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
+  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

data/vendor/choosealicense.com/_licenses/vim.txt

@@ -0,0 +1,111 @@
+---
+title: Vim License
+spdx-id: Vim
+
+description: There are no restrictions on using or distributing an unmodified copy of the software. Parts of the software may also be distributed, but the license text must always be included. For modified versions a few restrictions apply. The license is GPL compatible, you may compile the software with GPL libraries and distribute it.
+
+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
+
+permissions:
+  - commercial-use
+  - modifications
+  - distribution
+  - private-use
+
+conditions:
+  - include-copyright
+  - document-changes
+  - disclose-source
+  - same-license
+
+limitations: []
+
+---
+
+VIM LICENSE
+
+I)  There are no restrictions on distributing unmodified copies of [project]
+    except that they must include this license text.  You can also distribute
+    unmodified parts of [project], likewise unrestricted except that they must
+    include this license text.  You are also allowed to include executables
+    that you made from the unmodified [project] sources, plus your own usage
+    examples and Vim scripts.
+
+II) It is allowed to distribute a modified (or extended) version of [project],
+    including executables and/or source code, when the following four
+    conditions are met:
+    1) This license text must be included unmodified.
+    2) The modified [project] must be distributed in one of the following five
+       ways:
+       a) If you make changes to [project] yourself, you must clearly describe
+          in the distribution how to contact you.  When the maintainer asks
+          you (in any way) for a copy of the modified [project] you
+          distributed, you must make your changes, including source code,
+          available to the maintainer without fee.  The maintainer reserves
+          the right to include your changes in the official version of
+          [project].  What the maintainer will do with your changes and under
+          what license they will be distributed is negotiable.  If there has
+          been no negotiation then this license, or a later version, also
+          applies to your changes. The current maintainer is Bram Moolenaar
+          <Bram@vim.org>.  If this changes it will be announced in appropriate
+          places (most likely vim.sf.net, www.vim.org and/or comp.editors).
+          When it is completely impossible to contact the maintainer, the
+          obligation to send him your changes ceases.  Once the maintainer has
+          confirmed that he has received your changes they will not have to be
+          sent again.
+       b) If you have received a modified [project] that was distributed as
+          mentioned under a) you are allowed to further distribute it
+          unmodified, as mentioned at I).  If you make additional changes the
+          text under a) applies to those changes.
+       c) Provide all the changes, including source code, with every copy of
+          the modified [project] you distribute.  This may be done in the form
+          of a context diff.  You can choose what license to use for new code
+          you add.  The changes and their license must not restrict others
+          from making their own changes to the official version of [project].
+       d) When you have a modified [project] which includes changes as
+          mentioned under c), you can distribute it without the source code
+          for the changes if the following three conditions are met:
+          - The license that applies to the changes permits you to distribute
+            the changes to the Vim maintainer without fee or restriction, and
+            permits the Vim maintainer to include the changes in the official
+            version of [project] without fee or restriction.
+          - You keep the changes for at least three years after last
+            distributing the corresponding modified [project].  When the
+            maintainer or someone who you distributed the modified [project]
+            to asks you (in any way) for the changes within this period, you
+            must make them available to him.
+          - You clearly describe in the distribution how to contact you.  This
+            contact information must remain valid for at least three years
+            after last distributing the corresponding modified [project], or
+            as long as possible.
+       e) When the GNU General Public License (GPL) applies to the changes,
+          you can distribute the modified [project] under the GNU GPL version
+          2 or any later version.
+    3) A message must be added, at least in the output of the ":version"
+       command and in the intro screen, such that the user of the modified
+       [project] is able to see that it was modified.  When distributing as
+       mentioned under 2)e) adding the message is only required for as far as
+       this does not conflict with the license used for the changes.
+    4) The contact information as required under 2)a) and 2)d) must not be
+       removed or changed, except that the person himself can make
+       corrections.
+
+III) If you distribute a modified version of [project], you are encouraged to
+     use the Vim license for your changes and make them available to the
+     maintainer, including the source code.  The preferred way to do this is
+     by e-mail or by uploading the files to a server and e-mailing the URL. If
+     the number of changes is small (e.g., a modified Makefile) e-mailing a
+     context diff will do.  The e-mail address to be used is
+     <maintainer@vim.org>
+
+IV)  It is not allowed to remove this license from the distribution of the
+     [project] sources, parts of it or from a modified version.  You may use
+     this license for previous [project] releases instead of the license that
+     they came with, at your option.
+
+

data/vendor/choosealicense.com/_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

data/vendor/license-list-XML/src/0BSD.xml

@@ -0,0 +1,21 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<SPDXLicenseCollection xmlns="http://www.spdx.org/license">
+   <license isOsiApproved="true" licenseId="0BSD" name="BSD Zero Clause License">
+      <crossRefs>
+         <crossRef>http://landley.net/toybox/license.html</crossRef>
+      </crossRefs>
+    <text>
+      <copyrightText>
+         <p>Copyright (C) 2006 by Rob Landley &lt;rob@landley.net&gt;</p>
+      </copyrightText>
+
+      <p>Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is
+         hereby granted.</p>
+      <p>THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE
+         INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE
+         LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
+         FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
+         ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.</p>
+    </text>
+  </license>
+</SPDXLicenseCollection>