DeepSeek · DeepSeek Open Source License · View original document ↗

Derivative Works and Attribution Requirements

Medium severity High confidence Explicitdocumentlanguage Unique · 0 of 325 platforms
Share 𝕏 Share in Share 🔒 PDF
Monitor governance changes for DeepSeek 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 modify or redistribute DeepSeek-V3, you must include a copy of this license, display 'Built with DeepSeek-V3' prominently, keep all original copyright notices, state that you modified the model, and include 'DeepSeek-V3' in the name of your modified version.

This analysis describes what DeepSeek'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)

The attribution and naming requirements create affirmative branding obligations for any organization that distributes a modified version of the model. The requirement to use 'DeepSeek-V3' in the derivative model name may create trademark or brand-association considerations depending on the jurisdiction and the nature of the derivative product.

Consumer impact (what this means for users)

The agreement requires that any distributed derivative of DeepSeek-V3 carry the DeepSeek-V3 name and display an attribution notice, meaning that products built on modified versions of this model must publicly disclose their relationship to DeepSeek-V3.

Cross-platform context

See how other platforms handle Derivative Works and Attribution Requirements and similar clauses.

Compare across platforms →

Monitoring

DeepSeek 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 distribute or make available the Model Materials (or any derivative works thereof), you must (i) provide a copy of this Agreement; (ii) prominently display 'Built with DeepSeek-V3' on any derivative work; and (iii) if you modify the Model, you must (a) retain in the Model all pre-existing copyright notices; (b) add a statement that you have modified the Model; and (c) use the name 'DeepSeek-V3' in the name of your derivative model.

— Excerpt from DeepSeek's DeepSeek Open Source License

ConductAtlas Analysis

Institutional analysis (Compliance & governance intelligence)

REGULATORY LANDSCAPE: Attribution and naming requirements interact with trademark law in the EU, US, and other jurisdictions. The mandatory use of the 'DeepSeek-V3' name in derivative model names may raise trademark licensing questions, as the licensor does not appear to grant explicit trademark rights in the agreement text. The FTC's guidelines on endorsements and disclosures may also be relevant where attribution language could be interpreted as an endorsement. GOVERNANCE EXPOSURE: Medium. The naming requirement is operationally specific but creates product branding obligations that must be managed in release pipelines and product documentation. Non-compliance would constitute a license breach. JURISDICTION FLAGS: Trademark law jurisdiction varies by territory. Organizations in the EU should assess whether mandatory use of the 'DeepSeek-V3' name in a product name creates trademark dependency or conflicts with local brand protection strategies. US organizations should similarly assess trademark implications under the Lanham Act. CONTRACT AND VENDOR IMPLICATIONS: Software and AI product release processes should include a compliance checkpoint for DeepSeek-V3 attribution requirements. Procurement teams should ensure that downstream distributors and integration partners are contractually required to comply with the same attribution obligations. COMPLIANCE CONSIDERATIONS: Product and legal teams should develop a standard attribution compliance checklist for any product release that incorporates a derivative of DeepSeek-V3, including documentation review, naming verification, and license inclusion confirmation.

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
DeepSeek Open Source License
Entity
DeepSeek
Document last updated
May 11, 2026
Tracking information
First tracked
May 11, 2026
Last verified
May 12, 2026
Record ID
CA-P-010933
Document ID
CA-D-00784
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
5a1eeb26edc0314dea0217553f095f223998aa4e03f5f9f3c2df005738ccb28d
Analysis generated
May 11, 2026 12:01 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: DeepSeek
Document: DeepSeek Open Source License
Record ID: CA-P-010933
Captured: 2026-05-11 12:01:12 UTC
SHA-256: 5a1eeb26edc0314d…
URL: https://conductatlas.com/platform/deepseek/deepseek-open-source-license/derivative-works-and-attribution-requirements/
Accessed: May 13, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
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 DeepSeek's Derivative Works and Attribution Requirements clause do?

The attribution and naming requirements create affirmative branding obligations for any organization that distributes a modified version of the model. The requirement to use 'DeepSeek-V3' in the derivative model name may create trademark or brand-association considerations depending on the jurisdiction and the nature of the derivative product.

How does this clause affect you?

The agreement requires that any distributed derivative of DeepSeek-V3 carry the DeepSeek-V3 name and display an attribution notice, meaning that products built on modified versions of this model must publicly disclose their relationship to DeepSeek-V3.

Is ConductAtlas affiliated with DeepSeek?

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