How to Apply the Anti-996 License to Your Open Source Project

To apply the Anti-996 License to your project, copy the official LICENSE file from the 996.ICU repository into your root directory, add the shield badge to your README, and optionally combine it with other licenses like MIT.

The Anti-996 License is a draft open-source license created by the 996.ICU community to prohibit use of software by entities that violate labor-rights standards. When you apply the Anti-996 License to your repository, you signal commitment to fair labor practices while retaining software freedom for compliant users.

Step-by-Step Guide to Apply the Anti-996 License

1. Copy the Official License File

Download the LICENSE file from the upstream 996.ICU repository and place it unchanged in your project root. According to the source instructions, you must include the full "Anti 996 License Version 1.0 (Draft)" text exactly as provided.

curl -L https://raw.githubusercontent.com/996icu/996.ICU/master/LICENSE -o LICENSE
git add LICENSE
git commit -m "Add Anti-996 License"

The license text contains specific compliance conditions in lines 13-38 that prohibit use by companies violating labor laws. Do not modify these clauses when applying the license to your project.

2. Add the License Badge to Your README

Insert the official shield badge into your README.md to provide immediate visual identification of your licensing choice. The badge markdown is specified in externals/instruction.md at lines 18-23:

[![LICENSE](https://img.shields.io/badge/license-Anti%20996-blue.svg)](https://github.com/996icu/996.ICU/blob/master/LICENSE)

Place this snippet prominently near the top of your README, typically below the project title.

3. (Optional) Multi-License Your Project

You can dual-license or multi-license your project to combine the Anti-996 License with permissive licenses like MIT. The 996.ICU repository provides specific guidance in externals/instruction.md (lines 25-35) for two approaches:

Single file approach: Concatenate licenses with a clear delimiter.

MIT License
-----------

[MIT license text...]

---------- 
Anti-996 License Version 1.0 (Draft)
-----------------------------------
[Full text from the LICENSE file]

Separate files approach: Create distinct license files and reference them together.

curl -L https://raw.githubusercontent.com/996icu/996.ICU/master/LICENSE -o LICENSE.996ICU

# Create LICENSE.MIT with your MIT text

git add LICENSE.996ICU LICENSE.MIT
git commit -m "Add MIT + Anti-996 licenses"

4. Update Project Documentation

Add a explicit licensing statement to your README to clarify user obligations:

This project is licensed under the Anti-996 License. See [LICENSE](LICENSE) for details.

If your project serves Chinese-speaking communities, consider referencing the LICENSE_CN file (the Chinese translation available in the 996.ICU repository) in your documentation.

5. Commit and Verify

Add all new license files to version control and push to your remote repository. Verify that the license conditions (specifically the anti-labor-law clause in the LICENSE file, lines 13-38) are clearly accessible to potential users.

Key Source Files in the 996.ICU Repository

Understanding the source structure helps ensure correct application:

• LICENSE – Contains the complete "Anti 996 License Version 1.0 (Draft)" text. This is the canonical legal document you must copy.
• externals/instruction.md – Provides implementation guidance including badge markup (lines 18-23) and multi-licensing templates (lines 25-35).
• LICENSE_CN – The Chinese translation of the license text for multilingual projects.
• README.md – Demonstrates how the 996.ICU project displays its own licensing badge and instructions.

Summary

• Copy unchanged: Download the LICENSE file directly from 996icu/996.ICU without modifications.
• Display visibly: Add the shield badge from externals/instruction.md to your README for immediate recognition.
• Multi-license capable: Combine with MIT or other licenses using the delimiter method or separate files as documented in lines 25-35 of externals/instruction.md.
• Reference translations: Use LICENSE_CN for Chinese-language documentation when needed.
• Maintain compliance: Ensure the labor-rights conditions in lines 13-38 of the license remain intact and enforceable.

Frequently Asked Questions

Can I use the Anti-996 License together with MIT or GPL?

Yes. The 996.ICU repository explicitly supports multi-licensing. According to externals/instruction.md (lines 25-35), you can concatenate the Anti-996 License with MIT or other permissive licenses using a clear delimiter (----------) or maintain separate files (LICENSE.MIT and LICENSE.996ICU) and reference both in your documentation.

Do I need to modify the license text before applying it?

No. You must include the license text unchanged from the LICENSE file in the 996.ICU repository. The draft version 1.0 text contains specific anti-labor-law clauses (lines 13-38) that must remain intact to ensure the license functions as intended. Altering these provisions would invalidate the license's protective mechanisms.

Where can I find a Chinese translation of the license?

The Chinese translation is available in the LICENSE_CN file in the 996icu/996.ICU repository. This file contains the complete license text in Simplified Chinese, suitable for projects targeting Chinese-speaking developers or organizations.

What are the specific labor-rights conditions in the license?

The compliance conditions are detailed in lines 13-38 of the LICENSE file. These provisions prohibit use of the software by any individual or entity that violates local labor laws regarding working hours, compensation, or employment practices. Review these conditions carefully to ensure your project aligns with the license's ethical requirements before applying it.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}