How to Use Both Anti-996 License and Another License Together: A Dual-Licensing Guide

You can dual-license software under the Anti-996 License alongside conventional licenses like MIT or Apache-2.0 by keeping the Anti-996 text unmodified and adding a second license file, as the 996.ICU repository confirms this compatibility in its README and LICENSE files.

The 996icu/996.ICU repository hosts the Anti-996 License, a human-rights-oriented open-source license designed to prevent companies using illegal "996" work schedules from utilizing the software. If you want to use both Anti-996 License and another license together, the project explicitly supports this approach through dual licensing, provided you adhere to the display requirements specified in clause 1 of the license text.

Understanding Anti-996 License Compatibility

The Anti-996 License was drafted specifically to coexist with existing open-source ecosystems. According to the source code analysis, this compatibility is intentional and structural.

License Design and Origins

As documented in README.md, the license is "adapted from the MIT license" and explicitly "designed to be compatible with all major open-source licenses"【/cache/repos/github.com/996icu/996.ICU/master/README.md†L108-L109】. This foundational design means the Anti-996 License does not impose conflicting usage restrictions that would prevent combination with permissive or copyleft alternatives.

The Non-Negotiable Clause 1

The LICENSE file in the repository root contains a critical requirement that affects any dual-licensing strategy. Clause 1 states that the license must be displayed conspicuously and unmodified on every redistributed or derivative copy. This means:

• You cannot edit the Anti-996 license text when combining it with other licenses.
• The full LICENSE file must remain in your repository root.
• Any source file headers must preserve the Anti-996 notice in its original form.

Setting Up Dual Licensing in Your Project

To use both Anti-996 License and another license together, follow this structured implementation pattern derived from the repository's documentation and examples.

Step 1: Add Both License Files

Maintain separate files for each legal text. Keep the original LICENSE file containing the unmodified Anti-996 License, and add a second file such as LICENSE-MIT or LICENSE-APACHE containing your secondary license terms. This satisfies the Anti-996 requirement to display the license while clearly delineating the dual-licensing structure.

Step 2: Apply Combined License Headers

Insert a comment block at the top of each source file that references both licenses. Use the SPDX License Expression format for machine readability:

/**
 * @license
 * SPDX-License-Identifier: MIT AND Anti-996
 *
 * Copyright (c) 2024 [Author Name]
 *
 * Licensed under the MIT License (see LICENSE-MIT) and the Anti-996 License
 * (see LICENSE). The Anti-996 License must be displayed unchanged on any
 * redistribution, per clause 1 of that license.
 */

Adjust the comment syntax for your programming language while preserving the requirement to display the Anti-996 notice prominently.

Step 3: Update Documentation and Badges

Modify your README.md to display both license badges and explain the dual-licensing terms. The repository's own README.md provides a template for the Anti-996 badge syntax【/cache/repos/github.com/996icu/996.ICU/master/README.md†L10-L11】, which you can combine with your secondary license badge:

# My Project

[![Anti-996 License](https://img.shields.io/badge/license-Anti%20996-blue.svg)](LICENSE)
[![MIT License](https://img.shields.io/badge/license-MIT-lightgrey.svg)](LICENSE-MIT)

This repository is **dual-licensed** under the Anti-996 License and the MIT License.
You may redistribute the code under either license, provided you keep the
Anti-996 notice intact (see clause 1 of that license).

Step 4: Document the Dual-Licensing Intent

Create a NOTICE or NOTICE.md file clarifying that users may choose either license when redistributing. While optional, this prevents legal confusion:

## Dual Licensing Notice

The code in this repository is offered under two licenses:

* **Anti-996 License** – see `LICENSE`. This license **must be displayed
  unchanged** on any redistribution (clause 1).

* **MIT License** – see `LICENSE-MIT`. You may also redistribute under the
  terms of the MIT license.

You are free to choose **either** license when using the software.

Practical Implementation Examples

The awesomelist/README.md file in the repository demonstrates real-world projects that list both GPL-3.0 and Anti-996 licenses together, serving as a practical reference for badge placement and linking strategies.

Recommended Project Structure

my-project/
├── src/
│   └── main.js          # Source file with dual license header

├── LICENSE              # Anti-996 License (original, unmodified)

├── LICENSE-MIT          # MIT License text

├── README.md            # Badges and licensing explanation

└── NOTICE.md            # Optional detailed dual-licensing notice

SPDX Registration Considerations

If you require a standardized SPDX identifier for the Anti-996 License, follow the request process outlined in proposal/proposal_to_request_github_official_including_996icu_license.md【/cache/repos/github.com/996icu/996.ICU/master/proposal/proposal_to_request_github_official_including_996icu_license.md†L42-L45】. Until an official identifier is registered, use the descriptive format shown in the header examples above.

License Compatibility Considerations

When you use both Anti-996 License and another license together, understanding the interaction between license obligations is essential for compliance.

Permissive Licenses (MIT, Apache-2.0)

The Anti-996 License imposes no additional usage restrictions beyond its display requirements. When combined with MIT or Apache-2.0, the obligations stack simply: users must comply with the permissive license terms while maintaining the unmodified Anti-996 notice. No conflicts arise because neither license restricts the addition of attribution requirements.

Copyleft Licenses (GPL-3.0)

Dual licensing with GPL-3.0 requires careful attention to derivative works. While compatible, the copyleft license's source-disclosure requirements apply in addition to the Anti-996 display obligations. The combined work must carry both the GPL's copyleft provisions and the Anti-996 notice. The i18n/ko_KR.md file references alternative drafts and resources that may provide additional guidance for complex licensing scenarios.

Summary

• The Anti-996 License is explicitly designed to be compatible with all major open-source licenses, as stated in the 996.ICU README.md.
• Clause 1 requires the Anti-996 License text to remain unmodified and conspicuously displayed in any redistribution.
• Dual licensing requires separate license files (LICENSE for Anti-996, LICENSE-MIT or similar for the second license).
• Source files should contain headers referencing both licenses, using SPDX-License-Identifier format where possible.
• The proposal/proposal_to_request_github_official_including_996icu_license.md file contains guidance for obtaining official SPDX recognition.

Frequently Asked Questions

Can I modify the Anti-996 License text when combining it with another license?

No. Clause 1 of the Anti-996 License explicitly prohibits modification. You must include the license text exactly as it appears in the LICENSE file of the 996.ICU repository, displayed conspicuously on every copy. You may add a second license file, but you cannot edit the Anti-996 text to merge it with other legal terms.

Does dual licensing with Anti-996 require users to follow both licenses simultaneously?

Typically, dual licensing allows users to choose which license terms to follow. However, because the Anti-996 License contains the non-negotiable clause 1 requiring display of its text, users must satisfy that specific requirement regardless of which primary license they select for redistribution. The secondary license obligations apply only if the user chooses to operate under that license's terms.

Is there an SPDX identifier for the Anti-996 License?

As of the current repository state, the Anti-996 License does not have an official SPDX identifier. The file proposal/proposal_to_request_github_official_including_996icu_license.md outlines the process for requesting SPDX inclusion【/cache/repos/github.com/996icu/996.ICU/master/proposal/proposal_to_request_github_official_including_996icu_license.md†L42-L45】. Until registration is complete, use descriptive text in your SPDX headers rather than a standard short identifier.

Can I use Anti-996 with GPL-3.0 without violating the GPL?

Yes. The Anti-996 License's requirements (displaying the license text) do not conflict with GPL-3.0 provisions. When combining these licenses, ensure that the Anti-996 notice remains intact and conspicuous while also complying with GPL source code disclosure and copyleft requirements. The license does not impose additional usage restrictions that would create incompatibility with strong copyleft terms.

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