IBM Public License v1.0

Also known as IBM Public License 1.0, IBM Public License v1.0, IPL-1.0.

Commercial use: allowed
Share alike: required
Attribution: required (keep the copyright and license notices)

Compare with… Add to the compatibility check Download JSON-LD Turtle RDF/XML Text

Write this as a license text (needs an account) DALICC reads the model above and writes what it permits, requires and prohibits in plain English. Without an account, the Text download above writes the model out from the vocabulary.

Canonical URI https://dalicc.net/licenselibrary/IPL-1.0

Permissions

Change license from the text
Charge distribution fee from the text
Charge license fee from the text
Commercial use from the text
Derivative works from the text
Derive from the text
Duties
- Attribution from the text
- Modification notice from the text
- Notice from the text
- Share alike from the text
- Source code from the text
Display from the text
Distribute from the text
Duties
- Add statement from the text
- Attribution from the text
- Notice from the text
- Share alike from the text
- Source code from the text
Modified works from the text
Modify from the text
Duties
- Attribution from the text
- Modification notice from the text
- Notice from the text
- Share alike from the text
- Source code from the text
Patent grant from the text
Present from the text
Reproduce from the text
Sublicense from the text

Prohibitions

This license states no prohibitions.

License-wide duties

This license states no duties that apply to the work as a whole.

What applies by default

The statements above are the library's reading of this license: each is marked with the sentence it rests on, or as a library convention where the text is not explicit. The statements below are the ones the DALICC reasoner supplies for acts the license says nothing about, from the default rules of the dependency graph it reasons with. Each one names the legal source it rests on. None of it is in the record.

Promote by default rule (adopted)

This license says nothing about Promote, and the graph applies this reading in all jurisdictions it covers: it is not permitted unless the license permits it.

A licence that says nothing about endorsement is read as not allowing it: the licence gives the licensee no right to use the licensor's name or marks in a way that states or implies that the licensor endorses the licensee or its product, while stating truthfully that a work is based on or uses the licensed work is a different act that this rule does not decide. A copyright licence grants rights in the work, and the right to use a name or a trademark is a separate right under trademark law and the protection of names, which a silent copyright licence does not pass on. Combining a licence that is silent about endorsement with one that permits it shows a conflict marked as coming from this rule.

Basis Trademark and name rights are separate from copyright: Regulation (EU) 2017/1001 article 9 lets the proprietor of an EU trade mark prevent all third parties not having his consent from using the sign in the course of trade, and Directive (EU) 2015/2436 article 10, 15 U.S.C. 1114 and 1125(a), section 12 BGB and section 43 ABGB protect marks and names in the same way. The library's evidence is Creative Commons 4.0 section 2(b)(2): Patent and trademark rights are not licensed under this Public License. A copyright licence that is silent grants no right to use the licensor's name or marks to suggest endorsement (Worldwide)

Further terms

These are the things the license says about itself beyond the acts it permits, forbids and requires: when it ends, how long there is to put a breach right, which law governs it, and so on. A term that comes from the DALICC vocabulary links to its definition.

Patent license ends if you sue: Yes. Not a ban on suing: a patent claim over the work ends the patent license, or the whole license, as the text provides.
Terminates on breach: Yes

Clauses

Warranty disclaimer

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED ON AN "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED INCLUDING, WITHOUT LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.

Limitation of liability

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Additional clauses

A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that: a. it complies with the terms and conditions of this Agreement; and b. its license agreement: i. effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose; ii. effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits; iii. states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and iv. states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange. When the Program is made available in source code form: a. it must be made available under this Agreement; and b. a copy of this Agreement must be included with each copy of the Program. Each Contributor must include the following in a conspicuous location in the Program: Copyright (C) 1996, 1999 International Business Machines Corporation and others. All Rights Reserved. In addition, each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution. Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense. For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages. If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed. All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive. IBM may publish new versions (including revisions) of this Agreement from time to time. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. No one other than IBM has the right to modify this Agreement. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved. This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://spdx.org/licenses/IPL-1.0.html
Legal code: https://opensource.org/license/IPL-1.0
This description is published under: Creative Commons Attribution 4.0 International
Publisher: International Business Machines Corporation
Attribution name: IBM
SPDX identifier: IPL-1.0 on the SPDX license list
DALICC identifier: IPL-1.0

This record is published under CC BY 4.0. Credit it as: DALICC License Library, DALICC - Verein zur Förderung der Rechtssicherheit in der Datenbewirtschaftung, https://dalicc.net, CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). The license it describes belongs to its publisher.

Use this license

Everything below is generated from this record. Replace the example address with the address of your own work.

JSON sidecar

{
  "license-uri": "https://dalicc.net/licenselibrary/IPL-1.0",
  "license-title": "IBM Public License v1.0",
  "spdx-id": "IPL-1.0",
  "attribution": "Copyright (c) [year] [copyright holder]",
  "asset": null,
  "generated-by": "DALICC"
}

RDF, Turtle

@prefix cc: <http://creativecommons.org/ns#> .

<https://example.org/my-work>
    cc:license <https://dalicc.net/licenselibrary/IPL-1.0> .

RDF, JSON-LD

{
  "@context": {
    "cc": "http://creativecommons.org/ns#"
  },
  "@id": "https://example.org/my-work",
  "cc:license": {
    "@id": "https://dalicc.net/licenselibrary/IPL-1.0"
  }
}

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/IPL-1.0" rel="license">IBM Public License v1.0</a>.</p>

This license asks for attribution, so the credit line is part of it.

Badge

Markdown

[![License: IBM Public License v1.0](https://dalicc.net/license-library/IPL-1.0/badge.svg)](https://dalicc.net/license-library/IPL-1.0)

HTML

<a href="https://dalicc.net/license-library/IPL-1.0"><img src="https://dalicc.net/license-library/IPL-1.0/badge.svg" alt="License: IBM Public License v1.0"></a>

Review

Written from the license text by: Giray Havur
Written on: 2026-09-15
Second review: not yet done
Record changed since this review: yes (version 2, 2026-09-24)
Findings: 10 recorded, 7 applied to the record, 0 proposed

The IBM Public License is the Common Public License with IBM named as the initial contributor and the sole steward, and with one requirement added: every contributor must carry the IBM copyright legend in a conspicuous location. The record is CPL-1.0 plus a dalicc:addStatement duty on distribution. Nothing here is legal advice.

10 findings

info Rubric 2 odrl:target applied

dcmitype:Software alone, following EclipsePublicLicense10 and EPL-2.0, the two records of this family already in the library. The text licenses a Program, that is software in source code and object code form, so neither dalicc:CreativeWork nor dcmitype:Dataset is written.
major Rubric 3 odrl:permission applied

Section 2(a) grants the right "to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution", so dalicc:sublicense is a permission, and 2(b) grants a patent licence, so dalicc:patentGrant is one. The permissions are those of CPL-1.0.
major Rubric 4 odrl:prohibition applied

As in CPL-1.0: dalicc:ChangeLicense, because source form must be made available under this Agreement, and dalicc:patentRetaliationTermination from section 7. The text has no trademark clause, so dalicc:promote is not written.
major Rubric 5 odrl:duty applied

The one difference from CPL-1.0 is this sentence: "Each Contributor must include the following in a conspicuous location in the Program: Copyright (C) 1996, 1999 International Business Machines Corporation and others. All Rights Reserved." That is a dalicc:addStatement duty on odrl:distribute, on top of the share-alike, notice, attribution, source-code and modification-notice duties of CPL-1.0.
minor Rubric 6 dalicc:additionalClauses applied

Sections 5 and 6 are quoted into their own fields; they are word for word those of CPL-1.0. dalicc:additionalClauses carries section 3 including the legend, the commercial distribution indemnity, the patent litigation clause, the termination clause, the steward clause naming IBM and the governing-law clause.
info Rubric 7 cc:jurisdiction applied

New York law and the intellectual property laws of the United States, as in CPL-1.0. cc:jurisdiction stays dalicc:worldwide and the clause is quoted.
gap Rubric 8 dalicc:additionalClauses none

The same two gaps as CPL-1.0: the commercial distributor indemnity (proposed dalicc:commercialDistributorIndemnity) and the automatic termination (proposed dalicc:terminatesOnBreach).
info Rubric 10 family none

IPL-1.0 differs from CPL-1.0 in the definitions, which name IBM and the Original Program, in the steward clause and in the required legend. The records differ in exactly one triple, the dalicc:addStatement duty.
info Rubric 9 record none

The consistency check of app.services.composer with the axioms of dg_default returned an empty list for this record.
major Rubric 5 odrl:duty applied

Weak-copyleft family alignment of 2026-09-15: section 3 requires a distributor who distributes the Program in object code form to state that the source code is available and how to obtain it. The duty was on odrl:distribute alone; it is now also on odrl:modify and odrl:derive, which is where the other twenty-four records of the weak-copyleft family carry it, so a comparison of two of them shows a difference between the licences and not between two reviewers.

Report an issue The review record as JSON The review checks the model against the license text. It is not legal advice.

History

This license model has 2 versions. Version 2 is the one served today; every earlier version keeps its own address, so a conclusion drawn from one of them can still be checked against it.

Version 2 current2026-09-24 Giray Havur

The changes since version 1 recorded which sentence of the text each statement rests on and named the license the record itself is published under.

View version 2 JSON-LD Turtle RDF/XML
2 changes
- changed permission dalicc:sublicense
  
  was permission dalicc:sublicense
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form."
- added dct:license <https://creativecommons.org/licenses/by/4.0/>
  
  Manual edit Every record is published under CC BY 4.0. cc:license names the record DALICC keeps of that licence; dct:license now names it by the address Creative Commons publishes it at, so that a consumer matching the canonical IRI finds it.
Version 1

Created from the license text on 2026-09-15 (Eclipse, Common Public and Lucent).

View version 1 JSON-LD Turtle RDF/XML

Every change names the reason behind it: a finding of the content review, one of its library-wide decisions, the metadata that review wrote onto every record, or a hand edit. None of it is legal advice.

Nothing on this page is legal advice. What a license means is decided by its text; ask a legal advisor before you rely on it.