Blue Oak Model License 1.0.0

Also known as Blue Oak Model License 1.0.0, BlueOak-1.0.0.

Commercial use: allowed
Share alike: not 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/BlueOak-1.0.0

Permissions

Change license by library convention
Duties
- Use a compliant license by library convention
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
- Notice from the text
Display from the text
Distribute from the text
Duties
- Notice from the text
Modified works from the text
Modify from the text
Duties
- Notice from the text
Patent grant from the text
Present from the text
Reproduce 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.

Cure period: 30 days
Terminates on breach: Yes

Clauses

Warranty disclaimer

As far as the law allows, this software comes as is, without any warranty or condition, and no contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim.

Additional clauses

In order to receive this license, you must agree to its rules. The rules of this license are both obligations under that agreement and conditions to your license. You must not do anything with this software that triggers a rule that you cannot or will not follow. If anyone notifies you in writing that you have not complied with [Notices](#notices), you can keep your license by taking all practical steps to comply within 30 days after the notice. If you do not do so, your license ends immediately. No contributor can revoke this license.

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://spdx.org/licenses/BlueOak-1.0.0.html
Legal code: https://blueoakcouncil.org/license/1.0.0
This description is published under: Creative Commons Attribution 4.0 International
Publisher: Blue Oak Council
SPDX identifier: BlueOak-1.0.0 on the SPDX license list
DALICC identifier: BlueOak-1.0.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/BlueOak-1.0.0",
  "license-title": "Blue Oak Model License 1.0.0",
  "spdx-id": "BlueOak-1.0.0",
  "asset": null,
  "generated-by": "DALICC"
}

RDF, Turtle

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

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

RDF, JSON-LD

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

This license carries no attribution duty, so no credit line is offered here.

Badge

Markdown

[![License: Blue Oak Model License 1.0.0](https://dalicc.net/license-library/BlueOak-1.0.0/badge.svg)](https://dalicc.net/license-library/BlueOak-1.0.0)

HTML

<a href="https://dalicc.net/license-library/BlueOak-1.0.0"><img src="https://dalicc.net/license-library/BlueOak-1.0.0/badge.svg" alt="License: Blue Oak Model License 1.0.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: 11 recorded, 7 applied to the record, 0 proposed

The record models the Blue Oak Model License 1.0.0, a permissive license written in plain language. Each contributor licenses everything that would otherwise infringe their copyright and everything that would otherwise infringe their patent claims, so the record carries dalicc:patentGrant as a permission. The one condition is that everyone who gets a copy from you also gets the license text or a link to it, which is cc:Notice on distribute, modify and derive.

11 findings

major Rubric 3 odrl:permission applied

The copyright grant reads: "Each contributor licenses you to do everything with this software that would otherwise infringe that contributor's copyright in it." Everything means the full permissive set, including commercial use, both fee terms and modified and derivative works.
major Rubric 3 odrl:permission applied

The patent section reads: "Each contributor licenses you to do everything with this software that would otherwise infringe any patent claims they can license or become able to license." That is an express patent license, so dalicc:patentGrant is a permission. This and MulanPSL-2.0 are the two records of the review group that carry it.
major Rubric 5 odrl:duty applied

The Notices section reads: "You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to <https://blueoakcouncil.org/license/1.0.0>." cc:Notice on distribute, modify and derive. There is no cc:Attribution duty: the license asks for its own text, not for a credit to the author.
major Rubric 4 odrl:prohibition applied

dalicc:ChangeLicense is prohibited, because the license text has to reach every recipient. The review group notes expected a patent retaliation clause; version 1.0.0 has none, so dalicc:patentRetaliationTermination is not written. The only way to lose the license is to fail the Notices section and not cure it. (Corrected on 2026-09-15 by the verification pass: see the rubric 3 finding on relicensing below.)
gap Rubric 8 dalicc:additionalClauses none

The Excuse section is a cure period: a licensee notified in writing of a notices failure keeps the license by taking all practical steps to comply within 30 days, and loses it otherwise. That is termination on breach with a cure window, and no property can carry it. Proposed term: dalicc:terminatesOnBreach, a property over the existing dalicc:terminationOnBreach concept, with a companion for the cure period. Quoted in dalicc:additionalClauses, together with the Acceptance section and the irrevocability sentence.
minor Rubric 6 dalicc:WarrantyDisclaimer applied

The No Liability section is a single sentence covering both warranty and liability, so it is quoted whole into dalicc:WarrantyDisclaimer and dalicc:LiabilityLimitation is left out, the way the MIT record keeps one paragraph in one field. The three asterisks the source puts around the sentence are typographic emphasis and are dropped.
info Rubric 7 cc:jurisdiction none

The text names no legal system and no term, so cc:jurisdiction is dalicc:worldwide and dalicc:validityType is dalicc:perpetual. The Reliability section adds that "No contributor can revoke this license.", which is quoted; the library has a dalicc:irrevocable quality but no property to attach it to a record.
info Rubric 2 odrl:target applied

One odrl:AssetCollection of dct:type dcmitype:Software, following BSL-1.0. The text licenses software.
info Rubric 9 record none

The consistency check with the axioms of dg_default returned no conflicts.
info Rubric 10 record none

The closest existing record is BSL-1.0, which is also a short permissive license with a single notice condition. Blue Oak differs in granting patent rights expressly and in the cure period.
major Rubric 3 odrl:permission applied

Library convention 15: a licence that asks for no reciprocity and no source code asks only that the notice travels with the copy, which is a duty on the acts it governs and not a bar on putting the copy under other terms. dalicc:ChangeLicense is therefore a permission here, and the prohibition the earlier reading wrote is removed. The text reads: "Each contributor licenses you to do everything with this software that would otherwise infringe that contributor's copyright in it. ... You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license." The permission carries the dalicc:compliantLicense duty, as Apache-2.0 does, because the notice has to survive the relicensing.

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
6 changes
- changed permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]
  
  was permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]
  
  Manual edit The statement is marked as a library convention, family rule 15: Permissive records permit relicensing: the text does not state it in as many words. Its duty dalicc:compliantLicense is marked as a library convention, family rule 15: Permissive records permit relicensing.
- changed permission dalicc:patentGrant
  
  was permission dalicc:patentGrant
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Each contributor licenses you to do everything with this software that would otherwise infringe any patent claims they can license or become able to license."
- changed permission odrl:derive with duties [cc:Notice]
  
  was permission odrl:derive with duties [cc:Notice]
  
  Manual edit Its duty cc:Notice quotes "You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to <https://blueoakcouncil.org/license/1.0.0>."
- changed permission odrl:distribute with duties [cc:Notice]
  
  was permission odrl:distribute with duties [cc:Notice]
  
  Manual edit Its duty cc:Notice quotes "You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to <https://blueoakcouncil.org/license/1.0.0>."
- changed permission odrl:modify with duties [cc:Notice]
  
  was permission odrl:modify with duties [cc:Notice]
  
  Manual edit Its duty cc:Notice quotes "You must ensure that everyone who gets a copy of any part of this software from you, with or without changes, also gets the text of this license or a link to <https://blueoakcouncil.org/license/1.0.0>."
- 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 (Permissive: MIT, ISC and BSD-like).

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.