Meta · Llama Community License Agreement · View original document ↗

Attribution and Derivative Model Naming

Low severity High confidence Explicitdocumentlanguage Unique · 0 of 325 platforms
Share 𝕏 Share in Share 🔒 PDF
Recent governance activity Meta recorded 5 documented changes in the last 30 days.
Start monitoring updates
Monitor governance changes for Meta Create a free account to receive the weekly governance digest and monitor one platform for governance changes.
Create free account No credit card required.
Document Record

What it is

If you create and share a modified version of Llama 3, you must include the phrase 'Built with Meta Llama 3' in its documentation but cannot use the name 'Llama' or Meta's trademarks in the product name without Meta's written permission.

This analysis describes what Meta's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

This clause creates dual obligations for derivative model creators: a mandatory attribution requirement and a trademark restriction, meaning licensees must affirmatively identify their work as Llama-derived while simultaneously being prohibited from using Llama branding in product names without consent.

Consumer impact (what this means for users)

Developers releasing modified versions of Llama 3 must include 'Built with Meta Llama 3' attribution in their README documentation, which creates a visible disclosure of the model's origins for downstream users and developers who rely on that derivative model.

Cross-platform context

See how other platforms handle Attribution and Derivative Model Naming and similar clauses.

Compare across platforms →

Monitoring

Meta has changed this document before.

Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.

Start Watcher free trial Or create a free account →
▸ View Original Clause Language DOCUMENT RECORD
"
If you create derivative works or modifications based on Llama 3, you will not use the name 'Llama' or any other Meta trademark without prior written consent from Meta. If you create derivative works or modifications based on Llama 3 and distribute or make available such derivative works or modifications to third parties, you will add to such derivative works or modifications the following attribution in the relevant README: 'Built with Meta Llama 3'.

— Excerpt from Meta's Llama Community License Agreement

ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

(1) REGULATORY LANDSCAPE: Trademark law governs the restriction on using the 'Llama' name, and violations would be actionable under the Lanham Act in the US and equivalent trademark statutes in other jurisdictions. The EU AI Act's transparency requirements for general-purpose AI models may independently require disclosure of the underlying model used, potentially overlapping with this attribution requirement. (2) GOVERNANCE EXPOSURE: Low to Medium. The attribution requirement is operationally straightforward for organizations maintaining standard documentation practices, but the trademark restriction requires IP review of any product naming decisions involving derivative models. (3) JURISDICTION FLAGS: Trademark enforcement varies by jurisdiction; the restriction on using 'Llama' branding applies globally under the agreement but the practical enforcement of trademark rights depends on Meta's trademark registrations in specific countries. (4) CONTRACT AND VENDOR IMPLICATIONS: Organizations distributing derivative models to enterprise clients should ensure that client-facing documentation, model cards, and technical specifications include the required attribution. B2B contracts involving derivative model distribution should reference this obligation to ensure downstream compliance. (5) COMPLIANCE CONSIDERATIONS: IP and product teams should implement a review process for all derivative model releases to confirm attribution text is present in README files and that product names do not incorporate 'Llama' or other Meta trademarks without written consent.

Full compliance analysis

Regulatory citations, enforcement risk, and due diligence action items.

Track 1 platform — free Try Watcher free for 14 days

Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.

Provision details

Document information
Document
Llama Community License Agreement
Entity
Meta
Document last updated
May 11, 2026
Tracking information
First tracked
May 11, 2026
Last verified
May 12, 2026
Record ID
CA-P-011386
Document ID
CA-D-00777
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
916aa7b1c8f5e07d423f6713ddbbf3b69cb4288de094f9db4fcccb16aa539d2e
Analysis generated
May 11, 2026 13:21 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: Meta
Document: Llama Community License Agreement
Record ID: CA-P-011386
Captured: 2026-05-11 13:21:53 UTC
SHA-256: 916aa7b1c8f5e07d…
URL: https://conductatlas.com/platform/meta/llama-community-license-agreement/attribution-and-derivative-model-naming/
Accessed: May 13, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Low
Categories

Other risks in this policy

Professional Governance Intelligence

Need to monitor specific governance provisions?

Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.

Arbitration clauses AI governance Data rights Indemnification Retention policies
Start Professional free trial

Or start with Watcher →

Built from archived source documents, structured governance mappings, and historical version tracking.

Frequently Asked Questions

What does Meta's Attribution and Derivative Model Naming clause do?

This clause creates dual obligations for derivative model creators: a mandatory attribution requirement and a trademark restriction, meaning licensees must affirmatively identify their work as Llama-derived while simultaneously being prohibited from using Llama branding in product names without consent.

How does this clause affect you?

Developers releasing modified versions of Llama 3 must include 'Built with Meta Llama 3' attribution in their README documentation, which creates a visible disclosure of the model's origins for downstream users and developers who rely on that derivative model.

Is ConductAtlas affiliated with Meta?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Meta.