Anti-996 License Explained: How It Differs From the MIT License

The Anti-996 License is a permissive software license that adds labor-law compliance requirements and prohibits use by companies practicing the "996" work schedule (9 am–9 pm, 6 days a week), unlike the standard MIT License which imposes no such restrictions.

The Anti-996 License originated from the 996.ICU repository, a community-driven project advocating against illegal overtime work cultures in the tech industry. While it grants the same fundamental rights to use, modify, and distribute code as the MIT License, it introduces enforceable social-justice clauses that make it distinct from traditional permissive licenses. Understanding these differences is crucial for developers deciding which license to apply to their open-source projects.

What is the Anti-996 License?

The Anti-996 License is a custom open-source license housed in the LICENSE file at the root of the 996.ICU repository. It was designed specifically to combat the "996" work culture—referring to the schedule of 9 am to 9 pm, 6 days a week—that violates labor laws in many jurisdictions.

According to the source code in LICENSE, the license allows free use, modification, distribution, and sublicensing of the work, similar to other permissive licenses. However, it binds licensees to specific ethical obligations regarding labor practices and entity restrictions that go beyond conventional software licensing.

Key Differences Between Anti-996 and MIT Licenses

While both licenses provide broad permissions to use the software, the Anti-996 License introduces three critical constraints absent from the MIT License.

Labor Law Compliance Requirement

The Anti-996 License contains a mandatory labor-law compliance clause that requires the licensee to strictly comply with all applicable labor and employment laws of the jurisdiction where the entity or person is located or incorporated. This provision appears in lines 17-22 of the LICENSE file.

The standard MIT License contains no such obligation. Users of MIT-licensed software face no legal requirements regarding their internal employment practices or compliance with local labor regulations.

Prohibition of 996 Companies

Unlike the MIT License, which places no restrictions on specific entities, the Anti-996 License explicitly forbids use by a listed set of companies identified as practicing the 996 schedule. This blacklist appears in lines 7-15 of the LICENSE file.

This entity-specific restriction means that organizations engaging in documented 996 work practices cannot legally use software under this license, regardless of their willingness to comply with other terms. The MIT License imposes no comparable prohibitions on specific companies or individuals.

Display Requirements

The Anti-996 License mandates that the license text and notice must be conspicuously displayed on every redistributed copy (lines 13-15 of LICENSE). While the MIT License requires preservation of copyright notices, the Anti-996 License emphasizes prominent display of the full license text to ensure awareness of the labor-law obligations.

Compatibility and Dual Licensing

The 996.ICU project designed the Anti-996 License to be multi-licensed alongside permissive licenses like MIT. As noted in README.md (lines 103-106), projects can ship the Anti-996 text alongside a standard MIT License, allowing users to choose which terms govern their use.

The MIT License operates as a standalone permissive license without provisions for dual-licensing compatibility, though nothing prevents developers from offering MIT-licensed code under additional terms.

How to Apply the Anti-996 License

Developers can adopt the Anti-996 License either exclusively or in combination with the MIT License.

Single License Implementation

Place the full text from the LICENSE file at the root of your repository and add a header to each source file:

/*
 * Copyright (c) 2024 Your Name
 *
 * Licensed under the Anti-996 License (see LICENSE file for details).
 */

Dual Licensing with MIT

To offer users a choice between licenses, keep the LICENSE file (Anti-996) as-is and add a separate LICENSE.MIT file containing the standard MIT text. Reference both in your source headers:

/*
 * Copyright (c) 2024 Your Name
 *
 * Licensed under either:
 *   • the Anti-996 License (see LICENSE), or
 *   • the MIT License (see LICENSE.MIT).
 *
 * Choose whichever best fits your use-case.
 */

Both approaches satisfy the repository's requirement that the primary license be displayed prominently (lines 13-15 of LICENSE) and that a copy accompanies every distribution.

Summary

  • The Anti-996 License adds labor-law compliance requirements and prohibits use by companies practicing illegal 996 work schedules.
  • Unlike the MIT License, it mandates strict compliance with local employment laws and maintains a blacklist of prohibited entities.
  • The license requires conspicuous display of the full license text on every redistributed copy.
  • Projects can dual-license with MIT, offering users the choice of which terms to follow, as documented in README.md.
  • Both licenses share the same "as-is" warranty disclaimer and grant identical rights to use, modify, and distribute code.

Frequently Asked Questions

Is the Anti-996 License legally enforceable?

The Anti-996 License functions as a standard software license with additional contractual terms. While its enforceability depends on jurisdiction-specific contract and labor laws, the license text in LICENSE (lines 17-22) explicitly binds licensees to comply with applicable labor laws, creating a contractual obligation that courts could potentially enforce. However, the license has not been extensively tested in court, and its novel social-justice provisions may face legal scrutiny in different jurisdictions.

Can I use the Anti-996 License for commercial projects?

Yes, the Anti-996 License permits commercial use, modification, and distribution, similar to the MIT License. However, commercial entities must comply with the labor-law requirements and cannot use the software if they appear on the prohibited companies list (lines 7-15 of LICENSE). Businesses adopting this license must ensure their employment practices strictly adhere to local labor laws in every jurisdiction where they operate.

How do I check if my company is prohibited from using Anti-996 licensed software?

The prohibited entities are listed in lines 7-15 of the LICENSE file in the 996.ICU repository. The list includes companies documented as practicing the 996 work schedule. If your company appears on this blacklist, you cannot use software under the Anti-996 License unless the copyright holder grants you a separate license. Companies not on the list may use the software provided they comply with all other terms, including labor-law adherence.

What happens if I violate the Anti-996 License terms?

Violation of the Anti-996 License terms—such as failing to comply with labor laws or using the software while on the prohibited companies list—results in automatic termination of the rights granted by the license. While the license includes the standard warranty disclaimer (lines 40-46 of LICENSE), breach of the labor-law compliance clause or entity restrictions could expose the violator to copyright infringement claims by the licensor, in addition to any existing labor-law violations.

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:
curl -s "https://instagit.com/install.md"

Works with
Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →