diff options
| author | Leitwolf | 2026-11-15 22:58:40 +0300 |
|---|---|---|
| committer | GitHub | 2026-11-15 22:58:40 +0300 |
| commit | 21ce423a12523559abf83f7a2ed83e042efc418d (patch) | |
| tree | e83ae3454c5692f46c70876fb60fcc62828b2142 /LICENSES | |
| parent | 79f624d693b4fc3167c239c3eca47c858799333f (diff) | |
| parent | 2fbb5585e35078cb2490c8ae988860aa6dc0399d (diff) | |
| download | catch3-security/bounded-strings.tar.gz | |
Merge branch 'devel' into security/bounded-stringssecurity/bounded-strings
Diffstat (limited to 'LICENSES')
| -rw-r--r-- | LICENSES/AdditionRef-Progmasoft-Exception-1.1.txt | 80 | ||||
| -rw-r--r-- | LICENSES/AdditionRef-Progmasoft-Exception-2.0.txt | 118 | ||||
| -rw-r--r-- | LICENSES/AdditionRef-Progmasoft-Patent-Grant-1.1.txt | 101 | ||||
| -rw-r--r-- | LICENSES/GPL-3.0-or-later.txt | 674 | ||||
| -rw-r--r-- | LICENSES/LGPL-3.0-or-later.txt | 165 | ||||
| -rw-r--r-- | LICENSES/MPL-2.0.txt | 373 | ||||
| -rw-r--r-- | LICENSES/README.md | 19 |
7 files changed, 955 insertions, 575 deletions
diff --git a/LICENSES/AdditionRef-Progmasoft-Exception-1.1.txt b/LICENSES/AdditionRef-Progmasoft-Exception-1.1.txt deleted file mode 100644 index b9dab6e0..00000000 --- a/LICENSES/AdditionRef-Progmasoft-Exception-1.1.txt +++ /dev/null @@ -1,80 +0,0 @@ -Progmasoft Linking Exception, Version 1.1 - -This Exception is an additional permission to the Mozilla Public License, version 2.0 ("MPL-2.0"). It is intended to preserve MPL-2.0's file-level obligations for Covered Software while removing doubt about combining that software with independent code. Capitalized terms not defined here have the meanings given in MPL-2.0. - -1. Definitions - -"Independent Component" means software contained in one or more Source Code Form files that neither contain Covered Software nor are Modifications of Covered Software. A component does not cease to be independent merely because compilation, static or dynamic linking, loading, packaging, or deployment places its Executable Form in the same file, process, address space, archive, image, or distribution as Covered Software. - -"Combined Work" means a Larger Work that combines Covered Software with one or more Independent Components by any technical means, including static or dynamic linking, loading, embedding, plugins, extensions, language bindings, an API, ABI, FFI boundary, command-line interface, protocol, inter-process communication mechanism, or file format. - -"Output" means material produced by executing Covered Software, including generated source, object code, executable code, intermediate representations, documentation, reports, diagnostics, formatted text, and analysis results. - -2. Additional Permission for Combined Works - -Subject to compliance with MPL-2.0 for the Covered Software, each recipient has a worldwide, royalty-free, non-exclusive, irrevocable additional copyright permission to create, reproduce, use, modify, display, perform, make available, and distribute a Combined Work under terms of the recipient's choice, including proprietary or closed-source terms. - -Those chosen terms may govern Independent Components and other portions of the Combined Work, but must not restrict or alter any recipient's rights in the Covered Software under MPL-2.0 and this Exception. No distributor is required to relicense an Independent Component merely because it forms part of a Combined Work. - -3. Boundary of Covered Software - -Linking, loading, calling, communicating with, packaging, installing, or distributing an Independent Component with Covered Software does not, by itself: - -(a) make the Independent Component Covered Software or a Modification; -(b) subject the Independent Component's Source Code Form to MPL-2.0; or -(c) expand MPL-2.0 beyond files that are Covered Software or Modifications under MPL-2.0. - -If Source Code Form from Covered Software is copied into another file, or a new Source Code Form file contains Covered Software, MPL-2.0 determines whether that file is a Modification. Labels, file extensions, build boundaries, code generation, or later separation of files do not avoid that determination. - -4. Outputs - -An Output does not become Covered Software merely because Covered Software produced, transformed, linked, or processed it. The copyright license chosen for input material does not change merely because Covered Software processes that material. - -If an Output contains copyrightable Source Code Form or other copyrightable material copied or derived from Covered Software, this Exception does not remove MPL-2.0 obligations from that incorporated material. Facts, ideas, interfaces, names, signatures, diagnostics, and other material not protected by copyright are not converted into Covered Software by this Exception. - -5. Preservation of MPL-2.0 Obligations - -This Exception does not remove, replace, waive, or narrow any MPL-2.0 obligation applicable to Covered Software. In particular: - -(a) Covered Software in Source Code Form and every Modification remain subject to MPL-2.0; -(b) distribution in Executable Form remains subject to MPL-2.0 Section 3.2, including the obligation to inform recipients how to obtain the corresponding Source Code Form when that section applies; -(c) notices protected by MPL-2.0 Section 3.4 must be retained; and -(d) this Exception grants no permission to withhold Source Code Form that MPL-2.0 requires to be made available. - -Distribution of a Combined Work under terms of choice is permission for the Combined Work as a whole and its Independent Components. It is not permission to relicense a Covered Software file. - -6. Packaging and Deployment - -Placing Covered Software and an Independent Component in the same archive, package, installer, application bundle, container image, firmware image, distribution medium, hosted deployment, or process does not change their respective copyright licenses. Network interaction or operation as separate processes is not required for independence. - -7. Direct Grant to Recipients - -The additional permission in this Exception is granted directly by the copyright holders applying it to every recipient of the applicable Covered Software. A distributor need not sublicense this Exception. Distribution through one or more intermediaries does not reduce the permission, and termination of an upstream distributor's rights does not terminate rights already received by a compliant downstream recipient. - -8. Termination and Reinstatement - -This Exception has no separate patent-litigation, field-of-use, combination, or compatibility termination condition. A recipient may exercise it only while entitled to exercise the corresponding MPL-2.0 copyright rights. If those rights terminate under MPL-2.0 Section 5.1, exercise of this Exception for the affected Covered Software is suspended to the same extent and is reinstated when, and to the extent that, the MPL-2.0 rights are reinstated. - -A recipient may elect to use Covered Software under MPL-2.0 without relying on this Exception. - -9. Other Rights - -This Exception grants copyright permission only. It grants no trademark, trade dress, service mark, publicity, confidential-information, or patent rights. Patent rights, if any, arise only under MPL-2.0 or a separately applicable patent grant. Nothing in this Exception limits rights arising independently under exhaustion, fair use, fair dealing, implied license, estoppel, or other applicable law. - -10. Relationship to MPL-2.0 - -MPL-2.0 and this Exception are read together. If this Exception and MPL-2.0 cannot both be given effect with respect to the creation or distribution of a Combined Work, this Exception controls only to the minimum extent necessary to provide the additional permission stated in Sections 2 through 6. MPL-2.0 controls in every other respect. - -Nothing here changes whether Covered Software is "Incompatible With Secondary Licenses" or changes the operation of MPL-2.0 Section 3.3 for a work governed by a Secondary License. - -11. Applicability and Version - -This Exception applies only to a file that expressly identifies it with this exact SPDX license expression: - -MPL-2.0 WITH AdditionRef-Progmasoft-Exception-1.1 - -Reference to Version 1.1 does not incorporate any later version. A copy of this text supplied in a repository or distribution identifies the permission; the per-file expression determines which files receive it. - -12. Severability - -If any provision of this Exception is held unenforceable, it shall be reformed only to the minimum extent necessary to make it enforceable. If reformation is unavailable, that provision is severed and the remaining provisions continue to the maximum extent permitted by law. diff --git a/LICENSES/AdditionRef-Progmasoft-Exception-2.0.txt b/LICENSES/AdditionRef-Progmasoft-Exception-2.0.txt deleted file mode 100644 index a90676f7..00000000 --- a/LICENSES/AdditionRef-Progmasoft-Exception-2.0.txt +++ /dev/null @@ -1,118 +0,0 @@ -Progmasoft Linking Exception, Version 2.0 - -This Exception is an additional permission granted with the Mozilla Public License, version 2.0 ("MPL-2.0"). It keeps MPL-2.0's file-level copyleft for Covered Software and removes doubt about four things: combining Covered Software with other work, what compilers do to code, what programs built with Covered Software tools owe, and the interfaces other work needs in order to use Covered Software. It does not change the text of MPL-2.0. Capitalized terms not defined here have the meanings given in MPL-2.0, and "You" has the meaning given there. - -1. Definitions - -"Independent Work" means software or other material, in any form, that is neither Covered Software nor a Modification. Sections 3 and 5 say what does not change that. - -"Tool" means Covered Software that You run to produce material: a compiler, linker, code generator, build system, package manager, formatter, or similar program. - -"Input" means the material You give a Tool to process, other than the Tool's own files. - -"Output" means the material a Tool writes when it runs, including source code, intermediate representations, object code, executable code, packages, documentation, reports, diagnostics, formatted text, and analysis results. - -"Generated Code" means the part of an Output that a Tool copies, expands, or derives from its own Covered Software in its ordinary operation, rather than from Input. Examples are templates, parser skeletons, entry points, stubs, thunks, tables, metadata, instantiated generics, and project scaffolding. - -"Runtime Material" means Covered Software that (a) the copyright holders of a Tool identify, in the documentation they publish, as that Tool's runtime library or standard library, and (b) is compiled, linked, embedded into, or placed beside an Output because the Output uses it when it runs. A license text or other file installed for documentation only is not Runtime Material. - -"Interface Material" means declarations, type and data layouts, constants, enumerations, macros, function and method signatures, attributes, wire and file formats, and the short inline definitions that an interface needs in order to be used, to the minimum extent necessary to call, implement, extend, bind to, or interoperate with Covered Software. - -2. Larger Works - -You may create, reproduce, use, modify, make available, and distribute a Larger Work that combines Covered Software with Independent Work under terms of Your choice, including proprietary terms, provided You comply with MPL-2.0 for the Covered Software as this Exception adjusts it. The combination may be made by any technical means, including static or dynamic linking, loading, embedding, plugins, language bindings, an API, ABI, or FFI boundary, a command-line interface, a protocol, inter-process communication, or a file format. It does not matter whether the works end up in one file, process, address space, archive, image, or deployment. The word "separate" in the definition of Larger Work in MPL-2.0 Section 1.7 refers to Source Code Form. - -Your terms may govern the Independent Work and the Larger Work as a whole. They must not limit or alter a recipient's rights in the Source Code Form of the Covered Software. - -Neither MPL-2.0 nor this Exception requires You, for a Larger Work, to provide the Source Code Form of Independent Work, to provide object files or anything else that allows relinking, to allow reverse engineering of Independent Work, or to provide installation information, keys, or credentials. - -3. What Compilation Does Not Change - -The following do not make Independent Work into Covered Software or a Modification, and do not subject its Source Code Form to MPL-2.0: - -(a) calling, linking to, loading, subclassing, implementing, or otherwise using Covered Software through its interfaces; -(b) including, importing, or referring to a Covered Software header, module, or package from a file of Independent Work; and -(c) macro expansion, template or generic instantiation, specialization, inlining, link-time or whole-program optimization, just-in-time compilation, or any comparable compiler transformation that places Covered Software in the compiled form of Independent Work. - -Material placed in a compiled form under (c) is the Executable Form of the Covered Software it came from. Section 4 or Section 5 releases it when it is Generated Code, Runtime Material, or Interface Material. Otherwise MPL-2.0 Section 3.2 applies to it, and Section 7 says how to meet that Section. - -If You copy Covered Software in Source Code Form into a file, other than as Section 4 or Section 5 allows, that file is a Modification. Labels, file extensions, build boundaries, or later separation of files do not change that. - -4. Generated Code and Programs Built with Tools - -4.1 Output is not Covered Software merely because a Tool produced it. Running a Tool over Input does not change the license of the Input, and material in an Output that comes from Input has the same license as that Input. - -4.2 You may use, modify, and distribute Generated Code, in any form, under terms of Your choice. MPL-2.0 Sections 3.1 through 3.4 do not apply to it. You need not offer its source, keep its notices, or attribute it. - -4.3 You may distribute Runtime Material in Executable Form as part of, or together with, an Output that uses it, under terms of Your choice. MPL-2.0 Sections 3.1 through 3.4 do not apply to that distribution. The Source Code Form of Runtime Material stays under MPL-2.0, and this Section does not permit distributing Runtime Material on its own. This Section covers Runtime Material You have not changed, and a Modification of it only when You make that Modification available under Section 7. - -4.4 Limits. This Section 4 does not apply to: - -(a) Covered Software given to a Tool as Input, unless it is Runtime Material. Compiling, formatting, or transforming Covered Software with a Tool leaves its obligations in place; -(b) material that an unmodified Tool would not write for the same Input and options, unless You make the change that causes it available under Section 7. Changing a Tool so that it copies more of its Covered Software into Output does not widen this Section; or -(c) an Output produced for the purpose of obtaining a Tool's Covered Software rather than for using the Tool. Such material remains subject to MPL-2.0. - -4.5 Intermediate representations and every other kind of Output are treated alike. An Output keeps the permissions of this Section after it leaves You. If Your rights in a Tool end, that does not affect Output You have already made or the rights of anyone who received it. - -4.6 These permissions lift conditions; they do not end the license. Generated Code and Runtime Material stay licensed to You under MPL-2.0 Section 2, and MPL-2.0 Sections 6 and 7 continue to apply to them. - -5. Interface Material and Examples - -You may copy Interface Material into Independent Work, and translate it into another language, to the extent needed to use or interoperate with Covered Software. The result is not a Modification, and MPL-2.0 Section 3 does not apply to it, in Source Code Form or in Executable Form. This covers header files, bindings, and declarations in another language. It does not cover the implementation behind an interface. - -You may use, copy, and adapt code that the documentation of Covered Software presents as an example or as a starting point for Your own project, under terms of Your choice and without any obligation of MPL-2.0 Section 3. - -6. What This Exception Keeps - -Except where Sections 4 and 5 say otherwise: - -(a) Covered Software in Source Code Form, and every Modification, stay under MPL-2.0 and cannot be relicensed through this Exception; -(b) distributing Covered Software in Executable Form stays subject to MPL-2.0 Section 3.2, as Section 7 explains; -(c) notices protected by MPL-2.0 Section 3.4 stay in place in Source Code Form; and -(d) nothing here allows You to withhold Source Code Form that MPL-2.0 requires You to make available. - -7. Telling Recipients How to Obtain Source - -For Covered Software You have not changed, You satisfy MPL-2.0 Section 3.2(a) by giving recipients of the Executable Form a notice that names the Covered Software and its version and gives an address where the corresponding Source Code Form is publicly available. You may put that notice in documentation, in an about screen, in a notice file, or in a software bill of materials. The copyright holders' own public release of that version is a sufficient source; You need not host a copy, and You are not in breach if that release later stops being available. - -For a Modification, the same notice must give an address where the Source Code Form of the exact version You distributed can be obtained by reasonable means and in a timely manner. An address that follows a branch or otherwise changes over time is not enough. - -8. Contributors and Direct Grant - -Every Contributor who distributes Covered Software that carries an identification under Section 12 grants this Exception for that Contributor's Contributions. - -This Exception is granted directly to every recipient of Covered Software, for the duration of the copyright in it. A distributor need not sublicense it. Distribution through intermediaries does not reduce it, and the end of a distributor's rights does not end rights already received by others. - -You may use Covered Software under MPL-2.0 without relying on this Exception. As an exception to MPL-2.0 Section 3.4, You may remove the identification of this Exception from a file You modify; Your version of that file is then offered by You under MPL-2.0 alone. Earlier copies keep this Exception. - -9. Termination - -This Exception has no termination condition of its own. You may rely on Sections 2, 3, and 5 only while You hold the corresponding rights under MPL-2.0. If those rights end under MPL-2.0 Section 5.1 or 5.2, those permissions end for the affected Covered Software to the same extent, and return if and to the extent those rights are reinstated. This does not reach Independent Work, nor the rights of recipients that MPL-2.0 Section 5.3 preserves, nor Section 4.5. - -10. Relationship to MPL-2.0 - -MPL-2.0 and this Exception are read together. This Exception is a permission from copyright holders and is not a modified version of MPL-2.0. Where the two cannot both be given effect, this Exception controls only as far as needed to give the permissions in Sections 2 through 5 and 7 through 9, and MPL-2.0 controls in every other respect. This Exception continues to apply if You use Covered Software under a later version of the Mozilla Public License as MPL-2.0 Section 10.2 allows. - -MPL-2.0 Sections 6, 7, 8, and 9 apply to this Exception. It is provided without warranty. - -Nothing here changes whether Covered Software is "Incompatible With Secondary Licenses" or changes the operation of MPL-2.0 Section 3.3 for a work governed by a Secondary License. When You distribute under a Secondary License as that Section allows, the Secondary License governs that distribution. - -11. Other Rights - -This Exception concerns copyright only. It grants no trademark, trade dress, service mark, publicity, or confidential-information rights, and no patent rights beyond those MPL-2.0 or a separately applicable patent grant provides. Nothing here limits rights that arise independently under exhaustion, fair use, fair dealing, implied license, estoppel, or other applicable law. - -12. Applicability and Versions - -This Exception applies to Covered Software identified with this SPDX license expression, or an expression that contains it: - -MPL-2.0 WITH AdditionRef-Progmasoft-Exception-2.0 - -The identification may be in the file itself, in a companion license file, in a machine-readable file such as REUSE.toml that assigns the expression to that file, or in a notice of the project that names the file or the directory holding it. A compiled form has the identification of the source it was compiled from and does not need to carry it. - -Progmasoft may publish later versions of this Exception. You may use Covered Software under the version that identifies it or under any later version Progmasoft publishes. - -Progmasoft also grants this version for its own Contributions in every release it has made under Version 1.0 or Version 1.1 of this Exception. For those releases You may rely on either version. - -13. Severability - -If any provision of this Exception is held unenforceable, it shall be reformed only to the minimum extent necessary to make it enforceable. If reformation is unavailable, that provision is severed and the remaining provisions continue to the maximum extent permitted by law. diff --git a/LICENSES/AdditionRef-Progmasoft-Patent-Grant-1.1.txt b/LICENSES/AdditionRef-Progmasoft-Patent-Grant-1.1.txt new file mode 100644 index 00000000..2a0c5176 --- /dev/null +++ b/LICENSES/AdditionRef-Progmasoft-Patent-Grant-1.1.txt @@ -0,0 +1,101 @@ +Progmasoft Patent Grant, Version 1.1 + +This Patent Grant is a separate, additional permission. It does not replace, narrow, or condition the accompanying copyright license. + +1. Definitions + +"Covered Software" means the project-owned software expressly identified under Section 9 as covered by this Patent Grant. It excludes third-party material identified as such and software merely compatible or distributed with the Covered Software. + +"Progmasoft Contribution" means copyrightable software material authored by or on behalf of Progmasoft and included in Covered Software as distributed by Progmasoft. It includes later Progmasoft-authored modifications when they are distributed as Covered Software under Section 9. It does not include a recipient's or third party's modifications merely because they are based on, combined with, or distributed alongside Covered Software. + +"You" means the individual or Legal Entity exercising rights under this Patent Grant. "Legal Entity" includes an entity and every entity that controls, is controlled by, or is under common control with it. "Control" means direct or indirect power to direct management, or ownership of more than fifty percent of voting or beneficial interests. + +Progmasoft "Controls" a patent claim when Progmasoft has authority to grant the license in Section 3 without a duty to pay a third party for that grant, other than compensation owed to Progmasoft personnel. + +"Specified Combination" means only a particular combination that Progmasoft expressly designates by name and version, commit, release, or another unambiguous identifier in (a) the PATENTS notice accompanying Covered Software or (b) a public document that expressly states it is designating a "Specified Combination under the Progmasoft Patent Grant, Version 1.1." A general compatibility statement, example, test, API or ABI publication, protocol or file-format publication, SDK availability, interoperability claim, support statement, or distribution of software does not by itself create a Specified Combination. + +"Essential Claim" means a claim of a patent that Progmasoft Controls and that, absent the license in Section 3, would necessarily be infringed by making, having made, using, offering to sell, selling, importing, or otherwise transferring: + +(a) a Progmasoft Contribution as distributed by Progmasoft; or +(b) a Progmasoft Contribution as part of a Specified Combination. + +A claim is not an Essential Claim to the extent infringement arises only from a recipient or third-party modification, from an element not supplied in a Progmasoft Contribution, or from a combination that is not a Specified Combination. A claim does not cease to be Essential merely because the Covered Software is distributed in modified, source, object, or executable form, if the same claim would necessarily be infringed by the unmodified Progmasoft Contribution included in that form. + +2. Attachment and Effective Date + +For each Progmasoft Contribution, this Patent Grant becomes effective when Progmasoft first distributes that Contribution as Covered Software with the notice required by Section 9. + +For an Essential Claim that Progmasoft first Controls after that distribution, the grant becomes effective when Progmasoft first Controls the claim. Once a license to an Essential Claim becomes effective for a recipient, later transfer of the patent or cessation of Control does not revoke the recipient's license to the extent Progmasoft had authority to make it irrevocable. + +3. Patent License + +Subject only to Section 6, Progmasoft grants You a perpetual, worldwide, royalty-free, fully paid-up, non-exclusive patent license under the Essential Claims to make, have made for You, use, offer to sell, sell, import, and otherwise transfer Covered Software, either by itself or as part of a Specified Combination. + +The license is irrevocable except for the prospective automatic termination expressly and exclusively stated in Section 6. No fee, registration, notice, attribution beyond the accompanying copyright license, or separate agreement is required to receive or exercise it. + +4. Downstream Recipients and Distribution + +Every recipient receives the license in Section 3 directly from Progmasoft. A distributor is not required to sublicense Progmasoft patents or to grant rights in patents the distributor does not own or control. The license follows each authorized copy of Covered Software through any number of downstream distributions. + +A distributor may pass on this Patent Grant and its PATENTS notice unmodified. Additional terms imposed by a distributor cannot narrow the patent rights that a downstream recipient receives directly from Progmasoft. + +5. Independent Components, Modifications, and Outputs + +Independent software, libraries, modules, plugins, extensions, applications, and processes, including proprietary or closed-source components, are not licensed or subjected to the accompanying copyright license merely because they interact with Covered Software. + +Use with an Independent Component is licensed under Section 3 only when an Essential Claim is necessarily infringed by a Specified Combination. No patent license is implied for the Independent Component itself, for a recipient's modification as such, or for a combination that has not been expressly designated. + +Running Covered Software to compile, generate, transform, format, analyze, or otherwise process material does not impose the accompanying copyright license on resulting output merely because Covered Software produced it. This Patent Grant covers an output only to the extent the output itself is Covered Software under Section 9; it grants no patent rights in input material, independent output, or third-party technology. + +6. Defensive Termination + +If You initiate patent litigation in a court or administrative tribunal against Progmasoft or any other entity, alleging that Covered Software or a Progmasoft Contribution, as received from Progmasoft and without relying solely on an excluded modification or non-Specified Combination, directly or contributorily infringes a patent, every license granted to You under this Patent Grant terminates prospectively at the filing of that claim. + +Termination under this section applies only to You and the Legal Entities included within You. It does not terminate rights of a downstream recipient that did not initiate, direct, control, or voluntarily join the triggering claim. It does not rescind licenses for acts completed before termination and does not affect copyright permissions under the accompanying license. + +The following do not trigger termination: + +(a) a good-faith notice of a possible patent issue or a request to discuss licensing; +(b) participation in a standards, administrative examination, or opposition process that does not seek an infringement remedy against Covered Software; +(c) a declaratory-judgment claim brought solely in direct response to a written infringement threat concerning Your exercise of this Patent Grant; or +(d) a compulsory counterclaim, compulsory cross-claim, or defense asserted in response to patent litigation first initiated against You, provided that You do not seek affirmative relief beyond that necessary defense. + +If the triggering claim is voluntarily and permanently withdrawn, with prejudice where the applicable procedure permits, within sixty days after filing and before a judgment on the merits, the licenses terminated under this section are automatically reinstated prospectively on the date of withdrawal. Progmasoft may confirm additional reinstatement in a signed writing. No other act, omission, or circumstance permits revocation or termination of this Patent Grant. + +7. Patent Transfers and Successors + +To the extent legally permitted, Progmasoft shall not knowingly transfer a patent containing an Essential Claim unless the transfer is subject to licenses already granted under this Patent Grant or the transferee agrees in writing to honor them. A merger, reorganization, name change, or transfer of Covered Software does not itself terminate a license already received. + +This section creates no representation that Progmasoft owns any patent and no obligation to acquire, maintain, prosecute, or enforce a patent. + +8. Limits and Preserved Rights + +This Patent Grant applies only to claims Progmasoft has authority to license. It grants no rights in third-party patents, copyrights, trademarks, trade dress, service marks, confidential information, or other intellectual property. It provides no patent indemnity and no representation of non-infringement, validity, enforceability, or freedom to operate. + +No right is granted by implication beyond the express text. Nothing here limits any right You may independently have under patent exhaustion, implied license, estoppel, waiver, fair use, experimental use, or other applicable law. No failure or delay by Progmasoft to enforce a right expands or narrows this Patent Grant. + +This Patent Grant does not remove source-code availability, network-source, notice, attribution, or other obligations imposed by MPL-2.0, AGPL-3.0-or-later, or another accompanying copyright license. + +9. Applicability and Identification + +This Patent Grant applies only to software that, at the time Progmasoft distributes it: + +(a) is project-owned software in a repository, source distribution, or binary distribution containing a PATENTS notice that expressly identifies AdditionRef-Progmasoft-Patent-Grant-1.1 and provides this canonical text; or +(b) Progmasoft expressly identifies in a signed writing as Covered Software under that exact identifier. + +Reference to Version 1.1 does not incorporate any later version. Compatibility, use of the same API, ABI, protocol, file format, or SDK, presence in the same repository or distribution, or authorship or publication by Progmasoft does not by itself make other software Covered Software. + +Removal of the PATENTS notice from a later copy does not retroactively terminate rights already received for Covered Software, but it does not establish applicability to software that was not Covered Software when Progmasoft distributed it. + +SPDX custom addition identifier: AdditionRef-Progmasoft-Patent-Grant-1.1 + +10. Relationship to Copyright Permissions + +This Patent Grant is independent of the accompanying copyright license and any linking exception. Eligibility for or termination of this Patent Grant affects only the patent rights stated here. It does not terminate, restrict, or condition copyright permissions, and a copyright-license termination does not by itself terminate patent rights already granted here unless Section 6 applies. + +11. No Warranty; Severability + +The patent rights are granted without warranties or conditions of any kind. Warranty disclaimers and limitations of liability in the accompanying copyright license remain in effect. + +If a provision is held unenforceable, it shall be reformed only to the minimum extent necessary to make it enforceable. If reformation is unavailable, that provision is severed and the remaining provisions continue to the maximum extent permitted by law. + diff --git a/LICENSES/GPL-3.0-or-later.txt b/LICENSES/GPL-3.0-or-later.txt new file mode 100644 index 00000000..f288702d --- /dev/null +++ b/LICENSES/GPL-3.0-or-later.txt @@ -0,0 +1,674 @@ + GNU GENERAL PUBLIC LICENSE + Version 3, 29 June 2007 + + Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/> + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The GNU General Public License is a free, copyleft license for +software and other kinds of works. + + The licenses for most software and other practical works are designed +to take away your freedom to share and change the works. By contrast, +the GNU General Public License is intended to guarantee your freedom to +share and change all versions of a program--to make sure it remains free +software for all its users. We, the Free Software Foundation, use the +GNU General Public License for most of our software; it applies also to +any other work released this way by its authors. You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +them if you wish), that you receive source code or can get it if you +want it, that you can change the software or use pieces of it in new +free programs, and that you know you can do these things. + + To protect your rights, we need to prevent others from denying you +these rights or asking you to surrender the rights. Therefore, you have +certain responsibilities if you distribute copies of the software, or if +you modify it: responsibilities to respect the freedom of others. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must pass on to the recipients the same +freedoms that you received. You must make sure that they, too, receive +or can get the source code. And you must show them these terms so they +know their rights. + + Developers that use the GNU GPL protect your rights with two steps: +(1) assert copyright on the software, and (2) offer you this License +giving you legal permission to copy, distribute and/or modify it. + + For the developers' and authors' protection, the GPL clearly explains +that there is no warranty for this free software. For both users' and +authors' sake, the GPL requires that modified versions be marked as +changed, so that their problems will not be attributed erroneously to +authors of previous versions. + + Some devices are designed to deny users access to install or run +modified versions of the software inside them, although the manufacturer +can do so. This is fundamentally incompatible with the aim of +protecting users' freedom to change the software. The systematic +pattern of such abuse occurs in the area of products for individuals to +use, which is precisely where it is most unacceptable. Therefore, we +have designed this version of the GPL to prohibit the practice for those +products. If such problems arise substantially in other domains, we +stand ready to extend this provision to those domains in future versions +of the GPL, as needed to protect the freedom of users. + + Finally, every program is threatened constantly by software patents. +States should not allow patents to restrict development and use of +software on general-purpose computers, but in those that do, we wish to +avoid the special danger that patents applied to a free program could +make it effectively proprietary. To prevent this, the GPL assures that +patents cannot be used to render the program non-free. + + The precise terms and conditions for copying, distribution and +modification follow. + + TERMS AND CONDITIONS + + 0. Definitions. + + "This License" refers to version 3 of the GNU General Public License. + + "Copyright" also means copyright-like laws that apply to other kinds of +works, such as semiconductor masks. + + "The Program" refers to any copyrightable work licensed under this +License. Each licensee is addressed as "you". "Licensees" and +"recipients" may be individuals or organizations. + + To "modify" a work means to copy from or adapt all or part of the work +in a fashion requiring copyright permission, other than the making of an +exact copy. The resulting work is called a "modified version" of the +earlier work or a work "based on" the earlier work. + + A "covered work" means either the unmodified Program or a work based +on the Program. + + To "propagate" a work means to do anything with it that, without +permission, would make you directly or secondarily liable for +infringement under applicable copyright law, except executing it on a +computer or modifying a private copy. Propagation includes copying, +distribution (with or without modification), making available to the +public, and in some countries other activities as well. + + To "convey" a work means any kind of propagation that enables other +parties to make or receive copies. Mere interaction with a user through +a computer network, with no transfer of a copy, is not conveying. + + An interactive user interface displays "Appropriate Legal Notices" +to the extent that it includes a convenient and prominently visible +feature that (1) displays an appropriate copyright notice, and (2) +tells the user that there is no warranty for the work (except to the +extent that warranties are provided), that licensees may convey the +work under this License, and how to view a copy of this License. If +the interface presents a list of user commands or options, such as a +menu, a prominent item in the list meets this criterion. + + 1. Source Code. + + The "source code" for a work means the preferred form of the work +for making modifications to it. "Object code" means any non-source +form of a work. + + A "Standard Interface" means an interface that either is an official +standard defined by a recognized standards body, or, in the case of +interfaces specified for a particular programming language, one that +is widely used among developers working in that language. + + The "System Libraries" of an executable work include anything, other +than the work as a whole, that (a) is included in the normal form of +packaging a Major Component, but which is not part of that Major +Component, and (b) serves only to enable use of the work with that +Major Component, or to implement a Standard Interface for which an +implementation is available to the public in source code form. A +"Major Component", in this context, means a major essential component +(kernel, window system, and so on) of the specific operating system +(if any) on which the executable work runs, or a compiler used to +produce the work, or an object code interpreter used to run it. + + The "Corresponding Source" for a work in object code form means all +the source code needed to generate, install, and (for an executable +work) run the object code and to modify the work, including scripts to +control those activities. However, it does not include the work's +System Libraries, or general-purpose tools or generally available free +programs which are used unmodified in performing those activities but +which are not part of the work. For example, Corresponding Source +includes interface definition files associated with source files for +the work, and the source code for shared libraries and dynamically +linked subprograms that the work is specifically designed to require, +such as by intimate data communication or control flow between those +subprograms and other parts of the work. + + The Corresponding Source need not include anything that users +can regenerate automatically from other parts of the Corresponding +Source. + + The Corresponding Source for a work in source code form is that +same work. + + 2. Basic Permissions. + + All rights granted under this License are granted for the term of +copyright on the Program, and are irrevocable provided the stated +conditions are met. This License explicitly affirms your unlimited +permission to run the unmodified Program. The output from running a +covered work is covered by this License only if the output, given its +content, constitutes a covered work. This License acknowledges your +rights of fair use or other equivalent, as provided by copyright law. + + You may make, run and propagate covered works that you do not +convey, without conditions so long as your license otherwise remains +in force. You may convey covered works to others for the sole purpose +of having them make modifications exclusively for you, or provide you +with facilities for running those works, provided that you comply with +the terms of this License in conveying all material for which you do +not control copyright. Those thus making or running the covered works +for you must do so exclusively on your behalf, under your direction +and control, on terms that prohibit them from making any copies of +your copyrighted material outside their relationship with you. + + Conveying under any other circumstances is permitted solely under +the conditions stated below. |