Boost Software License 1.0

Also known as BSL-1.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/BSL-1.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
Duties
- Notice from the text
Derive from the text
Display from the text
Distribute from the text
Duties
- Notice from the text
Grant use from the text
Modify from the text
No-warranty notice from the text
Present from the text
Reproduce from the text

Prohibitions

Add statement from the text

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)

Clauses

Warranty disclaimer

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, TITLE AND NON-INFRINGEMENT.

Limitation of liability

IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: http://opensource.org/licenses/BSL-1.0
Legal code: http://opensource.org/licenses/BSL-1.0
This description is published under: Creative Commons Attribution 4.0 International
SPDX identifier: BSL-1.0 on the SPDX license list
DALICC identifier: BSL-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/BSL-1.0",
  "license-title": "Boost Software License 1.0",
  "spdx-id": "BSL-1.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/BSL-1.0> .

RDF, JSON-LD

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

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

Badge

Markdown

[![License: Boost Software License 1.0](https://dalicc.net/license-library/BSL-1.0/badge.svg)](https://dalicc.net/license-library/BSL-1.0)

HTML

<a href="https://dalicc.net/license-library/BSL-1.0"><img src="https://dalicc.net/license-library/BSL-1.0/badge.svg" alt="License: Boost Software License 1.0"></a>

Review

Status: Reviewed against the license text
Last checked: 2026-09-15
Reviewer: Giray Havur
Verdict: corrected during the review
Record changed since this review: yes (version 2, 2026-09-24)
Findings: 7 recorded, 4 applied to the record, 1 proposed

The Boost license grants use, reproduction, display, distribution, execution, transmission and derivative works, and lets the licensee pass those rights on to third parties, subject to one condition: the notice must travel with every copy except machine-executable object code. The record said the opposite of the text on passing rights on, and used cc:ShareAlike as a permission. Both were corrected.

7 findings

major Rubric 3 odrl:prohibition applied

The grant runs "to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so". The record prohibited odrl:grantUse, the exact opposite. Removed the prohibition and added the permission.
major Rubric 5 odrl:permission applied

cc:ShareAlike was modelled as a permission carrying a cc:Notice duty. cc:ShareAlike is a duty term: as a permission it means nothing the general grant does not already say, and the dependency graph treats an asserted share-alike as contradicting odrl:grantUse, which is why the record had to prohibit sublicensing to stay consistent. The Boost license imposes no share-alike. Removed. Flagged by the family conventions checked before the review.
minor Rubric 5 odrl:duty none

The notice condition has an exception the model cannot show: it does not apply "unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor". The cc:Notice duty on distribute is therefore stricter than the text for binary-only distribution.
minor Rubric 4 odrl:prohibition proposed

dalicc:addStatement and dalicc:promote remain prohibited with no support in the text. Library-wide default, left alone.
gap Rubric 8 vocabulary none

The object-code exception to the notice duty cannot be expressed. Proposed term: dalicc:sourceFormOnlyCondition, or a scope qualifier on the duty node.
minor Rubric 10 record applied

Standard-license addition of 2026-09-15, decision 9 and 10: the record was corrected against its new siblings and versioned. Library conventions 10 and 14: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE', and dct:publisher and cc:attributionName were the placeholder '- not specified - '.
minor Rubric 4 odrl:prohibition applied

dalicc:promote was prohibited and no sentence of this text supports it. The statement was the library's reading of a legal default, that a copyright licence which says nothing about endorsement grants no right to it, and it sat in 519 of 581 records as a house convention. That reading is now an adopted dalicc:DefaultRule of the core dependency graph, which supplies it to every licence that is silent about the action, so a compatibility check reaches the same answer and the record states only what the text states. Removed on 2026-09-23; see section 13 of docs/LICENSE_REVIEW.md.

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 content review of 2026-09-15 added 1 permission, removed 1 permission and 1 prohibition and recorded the review state. Later changes brought it in line with its family and its text in the verification of 2026-09-15, permitted relicensing with the notice as a duty, left endorsement to the default rule of the core dependency graph, 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
13 changes
- added dalicc:reviewStatus dalicc:Reviewed
  
  Review state Every record records how far it has come in the editorial workflow and when it was last checked against the legal text.
- added dalicc:reviewedOn "2026-09-15"^^xsd:date
  
  Review state Every record records how far it has come in the editorial workflow and when it was last checked against the legal text.
- removed permission cc:ShareAlike with duties [cc:Notice]
  
  Review finding cc:ShareAlike was modelled as a permission carrying a cc:Notice duty. cc:ShareAlike is a duty term: as a permission it means nothing the general grant does not already say, and the dependency graph treats an asserted share-alike as contradicting odrl:grantUse, which is why the record had to prohibit sublicensing to stay consistent. The Boost license imposes no share-alike. Removed. Flagged by the family conventions checked before the review.
- added permission odrl:grantUse
  
  Review finding cc:ShareAlike was modelled as a permission carrying a cc:Notice duty. cc:ShareAlike is a duty term: as a permission it means nothing the general grant does not already say, and the dependency graph treats an asserted share-alike as contradicting odrl:grantUse, which is why the record had to prohibit sublicensing to stay consistent. The Boost license imposes no share-alike. Removed. Flagged by the family conventions checked before the review.
- removed prohibition odrl:grantUse
  
  Review finding The grant runs "to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so". The record prohibited odrl:grantUse, the exact opposite. Removed the prohibition and added the permission.
- removed cc:attributionName "- not specified - "
  
  Manual edit Library conventions 10 and 14: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE', and dct:publisher and cc:attributionName were the placeholder '- not specified - '.
- added dalicc:LiabilityLimitation "IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
  
  Manual edit Library conventions 10 and 14: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE', and dct:publisher and cc:attributionName were the placeholder '- not specified - '.
- changed dalicc:WarrantyDisclaimer "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, TITLE AND NON-INFRINGEMENT."
  
  was dalicc:WarrantyDisclaimer "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, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE."
  
  Manual edit Library conventions 10 and 14: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE', and dct:publisher and cc:attributionName were the placeholder '- not specified - '.
- removed dct:publisher "- not specified - "
  
  Manual edit Library conventions 10 and 14: the disclaimer paragraph held the liability sentence, which begins 'IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE', and dct:publisher and cc:attributionName were the placeholder '- not specified - '.
- added permission dalicc:ChangeLicense with duties [dalicc:compliantLicense]
  
  Manual edit Permit relicensing on permissive licences; the notice clause is a duty, not a bar. 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 record carried before is removed. The text reads: "Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software ... to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following: The copyright notices in the Software and this entire statement ... must be included in all copies of the Software." The permission carries the dalicc:compliantLicense duty, as Apache-2.0 does, because the notice has to survive the relicensing.
- removed prohibition dalicc:promote
  
  Manual edit The endorsement prohibition rested on no sentence of the text; the default rule for endorsement now supplies it.
- 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.
- 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

The version this model had before the content review of 2026-09-15.

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.