Cryptographic Autonomy License 1.0 (Combined Work Exception)

Also known as CAL-1.0-Combined-Work-Exception, Cryptographic Autonomy License 1.0 (Combined Work Exception).

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/CAL-1.0-Combined-Work-Exception

Permissions

Change license from the text
Duties
- Use a compliant license from the text
Commercial use from the text
Derivative works from the text
Derive 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
Display from the text
Distribute from the text
Duties
- Add statement from the text
- Attribution from the text
- Notice from the text
- Provide user data from the text
- Source code from the text
Modified works from the text
Modify 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
Network use trigger from the text
Duties
- Provide user data from the text
- Source code from the text
Patent grant from the text
Present from the text
Reproduce from the text

Prohibitions

Add limitation from the text
Apply technical protection measures from the text
Promote from the text
Sublicense 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.

No default rule of that graph reaches this license: it speaks about every act the rules are about.

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

As far as the law allows, the Work comes AS-IS, without any warranty of any kind, and no Licensor or contributor will be liable to anyone for any damages related to this software or this license, under any kind of legal claim, or for any type of damages, including indirect, special, incidental, or consequential damages of any type arising as a result of this License or the use of the Work including, without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, loss of profits, revenue, or any and all other commercial damages or losses.

Additional clauses

Subject to the exception in section 4.4, You must provide to each Recipient a copy of, or no-charge unrestricted network access to, the Source Code corresponding to the Work ("Access").

Info

Target asset types: Software
Region / jurisdiction: Worldwide
Validity: Perpetual
Source: https://opensource.org/license/CAL-1.0
Legal code: http://cryptographicautonomylicense.com/license-text.html
This description is published under: Creative Commons Attribution 4.0 International
SPDX identifier: CAL-1.0-Combined-Work-Exception on the SPDX license list
DALICC identifier: CAL-1.0-Combined-Work-Exception

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/CAL-1.0-Combined-Work-Exception",
  "license-title": "Cryptographic Autonomy License 1.0 (Combined Work Exception)",
  "spdx-id": "CAL-1.0-Combined-Work-Exception",
  "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/CAL-1.0-Combined-Work-Exception> .

RDF, JSON-LD

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

HTML attribution

<p>This work is licensed under <a href="https://dalicc.net/licenselibrary/CAL-1.0-Combined-Work-Exception" rel="license">Cryptographic Autonomy License 1.0 (Combined Work Exception)</a>.</p>

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

Badge

Markdown

[![License: Cryptographic Autonomy License 1.0 (Combined Work Exception)](https://dalicc.net/license-library/CAL-1.0-Combined-Work-Exception/badge.svg)](https://dalicc.net/license-library/CAL-1.0-Combined-Work-Exception)

HTML

<a href="https://dalicc.net/license-library/CAL-1.0-Combined-Work-Exception"><img src="https://dalicc.net/license-library/CAL-1.0-Combined-Work-Exception/badge.svg" alt="License: Cryptographic Autonomy License 1.0 (Combined Work Exception)"></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: 13 recorded, 6 applied to the record, 0 proposed

Models the Cryptographic Autonomy License 1.0 as it applies to source files the licensor has marked with the Combined Work Exception. The modified source still goes out under the licence, but the rest of a Larger Work does not, so cc:ShareAlike is a duty on modify and derive rather than a license-wide duty. Everything else is identical to the CAL-1.0 record.

13 findings

info Rubric 1 spdx:licenseId none

File name, license id, SPDX id and IRI agree. cc:legalcode is the licensor's own URL and dct:source the OSI page, which lists both identifiers under one entry. dct:publisher is left out: the text names no steward.
info Rubric 2 odrl:target none

dcmitype:Software only, following MozillaPublicLicenseVersion20 and OSL-3.0.
major Rubric 3 odrl:permission applied

Section 3.1 grants 'the world-wide, royalty-free, non-exclusive permission to: a) Take any action with the Work that would infringe the non-patent intellectual property laws of any jurisdiction to which You are subject', together with a patent licence. Because the grant is stated as the whole of the non-patent rights, the record carries reproduce, distribute, modify, derive, display, present, commercial use, derivative works, modified works and dalicc:patentGrant. No distribution fee: the text is silent about charging for a copy and expressly requires no-charge network access to the source and a no-charge copy of user data.
major Rubric 6 dalicc:WarrantyDisclaimer applied

Section 6 is one sentence that disclaims warranty and limits liability together, so it is quoted whole into dalicc:WarrantyDisclaimer and dalicc:LiabilityLimitation is left out rather than duplicating the same words: 'As far as the law allows, the Work comes AS-IS, without any warranty of any kind, and no Licensor or contributor will be liable to anyone for any damages related to this software or this license'. Eleven further clauses are quoted in dalicc:additionalClauses.
minor Rubric 7 cc:jurisdiction applied

cc:jurisdiction stays dalicc:worldwide: section 3.1 grants world-wide permission and section 7.2 lets an individual licensor, not the licence, pick a forum and a governing law. The clause is quoted so a reader sees that the choice is open.
gap Rubric 8 odrl:duty none

Section 4.2.1 obliges the licensee to hand a recipient a copy of the recipient's own data: 'You must also provide to any Recipient to whom you provide services via the Work, a no-charge copy, provided in a commonly used electronic form, of the Recipient's User Data in your possession'. Nothing in the vocabulary comes near it. Quoted; proposed term: dalicc:provideUserData, an action used as a duty on odrl:distribute and on the network-use trigger.
major Rubric 4 odrl:prohibition applied

dalicc:applyTechnicalProtectionMeasures for section 4.2.2, which is the clearest case in the library for that term: 'You may not, by means of the use cryptographic methods applied to anything provided to the Recipient, by possession or control of cryptographic keys, seeds, hashes, by any other technological protection measures, or by any other method, limit a Recipient's ability to access any functionality present in Recipient's independent copy of the Work'. dalicc:sublicense for section 7.3 ('This License is not sublicensable'), dalicc:addLimitation for 4.2.3 and 7.3, dalicc:promote for 3.2(b) and dalicc:patentRetaliationTermination for 5.3.
gap Rubric 8 dalicc:additionalClauses none

The licence is triggered by deployment or by serving the work over a network, not only by distribution. The vocabulary has no term for that trigger, so the definition is quoted in dalicc:additionalClauses and the source-code duty is attached to distribute, modify and derive. Proposed term: dalicc:networkUseTrigger. Text: section 4.2.1, which binds You 'Throughout any period in which You exercise any of the permissions granted to You under this License' and reaches any Recipient 'to whom you provide services via the Work'.
gap Rubric 8 dalicc:additionalClauses none

Automatic termination on breach has no property that a record can carry: dalicc:terminationOnBreach is a policy quality with no predicate. The clause is quoted in dalicc:additionalClauses. Proposed term: dalicc:terminatesOnBreach as a boolean property on odrl:Set, with the cure period as a literal. Text: 'This License terminates automatically if You fail to comply with any of the conditions in section 4' (section 5.2), with a one-time reinstatement within sixty days.
info Rubric 9 record none

The consistency check of app.services.composer, run with the 39 axioms of licensedata/dependencygraph/dg_default.ttl, returned no conflicts.
major Rubric 5 odrl:duty applied

cc:ShareAlike hangs off odrl:modify and odrl:derive only, on the strength of section 4.5: 'any Source Code files marked by the Licensor as having the "Combined Work Exception" ... may be combined with other Software into a "Larger Work" ... any other Software in the Larger Work as well as the Larger Work as a whole may be licensed under the terms of your choice.' cc:SourceCode, cc:Attribution, cc:Notice and dalicc:addStatement keep the placement of the CAL-1.0 record.
minor Rubric 4 odrl:prohibition applied

No dalicc:ChangeLicense statement. Section 4.5 lets the Larger Work carry other terms while the marked source stays under the licence; the model has one relicensing statement for the whole policy and cannot scope it, so the record says nothing rather than saying something false in either direction, and quotes 4.5.
major Rubric 10 record none

Identical to CAL-1.0 except for the attachment level of cc:ShareAlike and the absence of the ChangeLicense prohibition. A consumer comparing the two records should read the quoted section 4.5, which is what the separate identifier stands for.

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, named the license the record itself is published under and removed the quotes that do not name the act they support.

View version 2 JSON-LD Turtle RDF/XML
5 changes
- changed permission odrl:derive with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  was permission odrl:derive with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "may be combined with other Software into a"
- changed permission odrl:modify with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  was permission odrl:modify with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "may be combined with other Software into a"
- 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.
- changed permission odrl:derive with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  was permission odrl:derive with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  Manual edit Removed the quoted evidence of permission odrl:derive, permission odrl:modify: the quoted sentence does not name the act. The statements stay, read from the text without a linked quote.
- changed permission odrl:modify with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  was permission odrl:modify with duties [cc:Attribution, cc:Notice, cc:ShareAlike, cc:SourceCode, dalicc:addStatement]
  
  Manual edit Removed the quoted evidence of permission odrl:derive, permission odrl:modify: the quoted sentence does not name the act. The statements stay, read from the text without a linked quote.
Version 1

Created from the license text on 2026-09-15 (Reciprocal and source-available).

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.