{"id":"Llama-3-Community-License","title":"Meta Llama 3 Community License Agreement","reviewed_on":"2026-09-22","reviewer":"Giray Havur","text_source":"https://raw.githubusercontent.com/meta-llama/llama3/main/LICENSE","text_retrieved":true,"verdict":"created","summary":"The second edition of the community licence, dated April 18, 2024, and the only one of the six whose retrieved copy carries the acceptable use policy in full. It adds to the first edition the duty to display a built-with line, the rule that a model trained on this one carries the name at the beginning of its own, and a narrow trademark licence for both. It keeps the bar on using the material or its outputs to improve another model, which the record carries as a dalicc:useForModelTraining prohibition.","findings":[{"rubric":1,"severity":"info","field":"dct:title","description":"File name, record identifier and IRI local name agree. The agreement has no SPDX identifier, so no spdx:licenseId triple is written. dct:title is the heading of the document; the short form, the full form and the model-hub tag are in dct:alternative.","action":"applied"},{"rubric":2,"severity":"major","field":"odrl:target","description":"dcmitype:Dataset and dcmitype:Software. The licensed material is defined as \"collectively, Meta's proprietary Meta Llama 3 and Documentation (and any portion thereof) made available under this Agreement\", and Meta Llama 3 is defined as \"the foundational large language models and software and algorithms, including machine-learning model code, trained model weights, inference-enabling code, training-enabling code, fine-tuning enabling code and other elements of the foregoing\": trained weights are data, the code is software, and the documentation travels with both.","action":"applied"},{"rubric":3,"severity":"major","field":"odrl:permission","description":"Clause 1.a grants \"a non-exclusive, worldwide, non-transferable and royalty-free limited license under Meta's intellectual property or other rights owned by Meta embodied in the Llama Materials to use, reproduce, distribute, copy, create derivative works of, and make modifications to the Llama Materials.\" That gives odrl:reproduce, odrl:distribute, odrl:modify, odrl:derive, cc:DerivativeWorks and dalicc:ModifiedWorks. cc:CommercialUse is permitted because the agreement names no limit of purpose and instead writes its commercial limit as a user threshold in clause 2, which is quoted and reported as a gap. dalicc:useForModelTraining is prohibited rather than permitted; see rubric 4. dalicc:networkUseTrigger carries clause 1.b.i, which reaches \"a product or service that uses any of them, including another AI model\", and it carries the same duties as distribution. dalicc:sublicense is left out in either position: the grant is \"non-transferable\" but the agreement says nothing about sublicensing.","action":"applied"},{"rubric":4,"severity":"major","field":"odrl:prohibition","description":"Four prohibitions. dalicc:useForModelTraining from clause 1.b.v, \"You will not use the Llama Materials or any output or results of the Llama Materials to improve any other large language model (excluding Meta Llama 3 or derivative works thereof).\" The exclusion is quoted with the clause: training a derivative of this model is inside the grant, training a competing one is not. dalicc:ChangeLicense because the agreement must travel with the material and the text gives no leave to put it under other terms. dalicc:promote from clause 5.a, \"No trademark licenses are granted under this Agreement\". dalicc:patentRetaliationTermination from clause 5.c, under which litigation alleging that the material or its outputs infringe your rights ends every licence granted by the agreement; the clause is wider than patents and ends the whole agreement, which is what the term allows for.","action":"applied"},{"rubric":5,"severity":"major","field":"odrl:duty","description":"Five duties on odrl:distribute, the same five on dalicc:networkUseTrigger, and one licence-wide duty. cc:Notice comes from clause 1.b.i(A), the duty to \"provide a copy of this Agreement with any such Llama Materials\". dalicc:addStatement comes from clause 1.b.i(B), the duty to \"prominently display “Built with Meta Llama 3” on a related website, user interface, blogpost, about page, or product documentation\". cc:Attribution and dalicc:includeNoticeFile come from clause 1.b.iii, the attribution notice \"within a “Notice” text file distributed as a part of such copies\". cc:ShareAlike carries the fact that the agreement travels with the material and with any derivative works thereof. The licence-wide duty is dalicc:exportControlNotice, from clause 1.b.iv. The duties hang on dalicc:networkUseTrigger as well because clause 1.b.i reaches \"a product or service that uses any of them, including another AI model that uses any of them\".","action":"applied"},{"rubric":6,"severity":"minor","field":"dalicc:WarrantyDisclaimer","description":"Clause 3 goes to dalicc:WarrantyDisclaimer and clause 4 to dalicc:LiabilityLimitation, each whole and verbatim. dalicc:additionalClauses carries the definitions, the acceptance sentence, the grant and the redistribution conditions, the additional commercial terms, the intellectual property clause, the term and termination clause, the governing law clause and the acceptable use policy in full. Curly quotation marks in the source are kept.","action":"applied"},{"rubric":7,"severity":"minor","field":"cc:jurisdiction","description":"cc:jurisdiction is dalicc:worldwide, from the worldwide grant, while dalicc:governingLaw names California: \"This Agreement will be governed and construed under the laws of the State of California without regard to choice of law principles\". The two are different things and both are stated. dalicc:validityType is dalicc:perpetual, because the term runs from acceptance until terminated rather than for a fixed period, and dalicc:terminatesOnBreach is true from \"Meta may terminate this Agreement if you are in breach of any term or condition of this Agreement.\" No cure period is given.","action":"applied"},{"rubric":8,"severity":"gap","field":"dalicc:additionalClauses","description":"The commercial limit is a user threshold, and no term can hold it: \"If, on the Meta Llama 3 version release date, the monthly active users of the products or services made available by or for Licensee, or Licensee's affiliates, is greater than 700 million monthly active users in the preceding calendar month, you must request a license from Meta, which Meta may grant to you in its sole discretion, and you are not authorized to exercise any of the rights under this Agreement unless or until Meta otherwise expressly grants you such rights.\" Neither cc:CommercialUse nor dalicc:fieldOfUseRestriction says \"above this size the grant stops\". Quoted; the proposed term is dalicc:scaleThresholdCondition, an annotation carrying the measure and the number.","action":"none"},{"rubric":8,"severity":"gap","field":"dalicc:fieldOfUseRestriction","description":"The acceptable use policy is printed after the agreement and is incorporated by reference by clause 1.b.iv. It lists three groups of prohibited uses, from violating the law and the rights of others to activities that risk death or bodily harm and to deceiving or misleading others. dalicc:fieldOfUseRestriction names the field in a short literal, not a list, so the whole policy is quoted verbatim in dalicc:additionalClauses. The proposed term is dalicc:prohibitedUsePolicy, an annotation carrying the list or the address of the policy a licence applies.","action":"none"},{"rubric":8,"severity":"gap","field":"dalicc:additionalClauses","description":"Clause 1.b.i ends with a naming rule that no duty action carries: \"If you use the Llama Materials to create, train, fine tune, or otherwise improve an AI model, which is distributed or made available, you shall also include \"Llama 3\" at the beginning of any such AI model name.\" dalicc:rename asks for a name that distinguishes the changed work from the original; this asks for the opposite, a name that ties it to the original. dalicc:addStatement carries the \"Built with Meta Llama 3\" line but not the prefix. Quoted; the proposed term is dalicc:derivativeNamingRequirement, a duty action.","action":"none"},{"rubric":9,"severity":"info","field":"record","description":"The consistency check of app.services.composer against dg_default returned an empty conflict list. The cc:ShareAlike duty sits on the acts rather than on the odrl:Set, so it does not meet the dalicc:ChangeLicense prohibition in the rule about whole-work reciprocity.","action":"none"},{"rubric":10,"severity":"info","field":"record","description":"Family: the second of the six and the turning point. It adds the built-with duty, the naming rule and dalicc:networkUseTrigger to the first edition, and it is the last of the six to prohibit dalicc:useForModelTraining: the third edition drops clause 1.b.v and instead contemplates training another model, subject to the naming rule. This is also the only edition whose title carries the publisher's name.","action":"none"},{"rubric":5,"severity":"major","field":"odrl:duty","description":"The agreement must accompany the Llama Materials and derivative works, but the text does not require a derivative to be licensed under it: clause 1.b.i reads \"If you distribute or make available the Llama Materials (or any derivative works thereof), or a product or service that uses any of them, including another AI model, you shall (A) provide a copy of this Agreement with any such Llama Materials; and (B) prominently display “Built with Meta Llama 3” on a related website, user interface, blogpost, about page, or product documentation.\" The record therefore carries a notice duty and not share alike. The cc:ShareAlike duty is removed from the acts it hung on, and the dalicc:ChangeLicense prohibition written on 2026-09-22 is replaced by a dalicc:ChangeLicense permission with the dalicc:compliantLicense duty, as Apache-2.0 carries it: a derivative may be offered under other terms as long as the copy of the agreement and the notice travel with the Llama Materials. The cc:Notice duty the record carries already states that the copy must travel.","action":"applied"}],"family":"Model licences","port_of":null,"variant_kind":null,"variant_of":null,"notes":"Modelled from the licence file in the publisher's source repository, which carries the agreement and the acceptable use policy in one file. cc:legalcode points at the raw file and dct:source at the same file in its repository. The policy is quoted in full as the last literal of dalicc:additionalClauses because the retrieved text contains it; the other five records of this family link to it instead, because their files do not."}