DeepSeek updated the LICENSE file for its DeepSeek-R1 model on May 15, 2026. The change removed three sentences that previously appeared in the GitHub repository's LICENSE display: one sentence clarifying that licensed works and modifications may be distributed under different terms without source code, and two sentences describing permissions and limitations. The core MIT License text and liability disclaimer remain unchanged. The practical effect is that the repository's LICENSE file now displays only the standard MIT License text without the supplementary explanatory language that was previously visible.
This change does not materially affect consumer rights or obligations. The underlying MIT License that governs the DeepSeek-R1 model remains in effect unchanged. The removal of supplementary explanatory text from the GitHub repository display does not modify what users are permitted to do with the software, only how the license terms are presented in the repository interface. Users retain all permissions and limitations established by the MIT License itself.
This change affects how the MIT License governing DeepSeek-R1 is presented in the repository, but does not alter the substantive rights, permissions, or limitations that the license grants. The removal of explanatory text may reduce clarity for developers unfamiliar with the MIT License, but the underlying open-source framework remains unchanged.
Unchanged; the license text permitting commercial use, modification, distribution, and private use remains in effect.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
This change is a formatting and display modification to the GitHub repository license documentation, not a substantive alteration of the MIT License governing the DeepSeek-R1 model. The core MIT License text, permissions, and liability disclaimers are unchanged. No new compliance obligations are created. Organizations using or distributing the DeepSeek-R1 model continue to operate under the existing MIT License framework. This does not require escalation unless your organization has specific documentation or audit requirements tied to how the license is displayed in the repository.
Full compliance analysis
Obligation analysis, escalation trigger, board language, and recommended action.
Monitor: regulatory citations + obligations. Compliance: full compliance memo.
ConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-C-002129.
Severity increased from medium to high, indicating DeepSeek elevated the importance of acceptable use compliance.
7 provisions unchanged.
Cross-platform context
See how other platforms handle similar provisions across the ConductAtlas archive.
See the full side-by-side comparison of every sentence added, removed, and modified.
🔒 Full diff — MonitorThe detected change shows a single metadata update to the DeepSeek-R1 LICENSE file on GitHub: the issue count changed from …
The detected change shows a minor metadata update in DeepSeek's public repository interface: the pull request count changed from 25 …
DeepSeek modified the MIT License file documentation on its DeepSeek-R1 repository on June 29, 2026. The change removed supplementary explanatory …
Buried in Robinhood's customer agreement is broad authority to close your positions, suspend your account, and force arbitration. Here is w…
Stripe's terms authorize fund reserves, payout withholding, and account termination. Here is what the agreement states and what business ow…
Get alerted when this policy changes again — including what changed and why it matters.
Prefer a weekly summary instead?
Get the biggest policy changes across 320+ platforms every Sunday.