MIT No Attribution

Also known as MIT No Attribution, MIT-0.

Commercial use: allowed
Share alike: not required
Attribution: not required

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/MIT-0

Permissions

Change license by library convention
Charge distribution fee from the text
Commercial use from the text
Derivative works from the text
Derive from the text
Display from the text
Distribute from the text
Grant use from the text
Modified works from the text
Modify 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)

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 AND NONINFRINGEMENT.

Limitation of liability

IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF 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: https://spdx.org/licenses/MIT-0.html
Legal code: https://github.com/aws/mit-0
This description is published under: Creative Commons Attribution 4.0 International
Publisher: Amazon Web Services
SPDX identifier: MIT-0 on the SPDX license list
DALICC identifier: MIT-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/MIT-0",
  "license-title": "MIT No Attribution",
  "spdx-id": "MIT-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/MIT-0> .

RDF, JSON-LD

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

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

Badge

Markdown

[![License: MIT No Attribution](https://dalicc.net/license-library/MIT-0/badge.svg)](https://dalicc.net/license-library/MIT-0)

HTML

<a href="https://dalicc.net/license-library/MIT-0"><img src="https://dalicc.net/license-library/MIT-0/badge.svg" alt="License: MIT No Attribution"></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: 9 recorded, 5 applied to the record, 0 proposed

The record models MIT without its one condition. The grant is the MIT grant minus the notice requirement, so the record carries the permissions of the MIT record and no duty at all, which is the whole difference between the two licenses. Sublicensing and relicensing are permitted, as on Cc010Universal, because nothing has to travel with a copy.

9 findings

major Rubric 3 odrl:permission applied

The grant reads: "Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so." The record therefore permits reproduce, distribute, modify, derive, display, present, grantUse, sublicense, commercial use, derivative works, modified works and the distribution fee. The grant names sublicensing in as many words, so dalicc:sublicense is a permission, and the clause that lets the recipient of a copy do the same is odrl:grantUse, the term the MIT record already uses for it.
major Rubric 3 odrl:permission applied

dalicc:ChangeLicense is permitted, following Cc010Universal: the grant carries no condition, so a licensee may put a copy under other terms. This is the one statement that separates MIT-0 from MIT in a compatibility result, together with the absence of duties.
major Rubric 5 odrl:duty applied

No duties. The sentence that carries the MIT notice condition, "The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software", is absent from this text, which is why the license exists.
info Rubric 4 odrl:prohibition none

No prohibitions. The text has no trademark, endorsement or advertising clause, so dalicc:promote is not prohibited even though most permissive records carry it.
minor Rubric 6 dalicc:WarrantyDisclaimer applied

The disclaimer paragraph holds two sentences: the warranty disclaimer and the liability limitation. They are quoted into dalicc:WarrantyDisclaimer and dalicc:LiabilityLimitation respectively. The MIT record keeps both sentences in dalicc:WarrantyDisclaimer and leaves dalicc:LiabilityLimitation empty, so the two records split the same paragraph differently.
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.
info Rubric 2 odrl:target applied

One odrl:AssetCollection of dct:type dcmitype:Software, following MIT. The text licenses software and its documentation.
info Rubric 9 record none

The consistency check with the axioms of dg_default returned no conflicts. No share-alike duty is present, so permitting dalicc:ChangeLicense raises no conflict.
info Rubric 10 record none

MIT-0 is MIT minus the notice condition, not a version of MIT, so the record carries no dalicc:variantKind. Read against MIT the difference is: no cc:Attribution and no cc:Notice duty anywhere, and dalicc:ChangeLicense permitted.

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
4 changes
- changed permission dalicc:ChangeLicense
  
  was permission dalicc:ChangeLicense
  
  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.
- changed permission dalicc:sublicense
  
  was permission dalicc:sublicense
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so."
- changed permission odrl:grantUse
  
  was permission odrl:grantUse
  
  Manual edit The statement now quotes the sentence of the licence text it rests on: "Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so."
- 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.