Anti-996 License vs GPL and Apache: Key Differences Explained

The Anti-996 License is a purpose-specific open-source license that adds labor-law compliance requirements to software usage, whereas GPL and Apache licenses focus solely on software freedom and intellectual property rights without addressing workers' rights.

The 996.ICU repository created the Anti-996 License to protest the illegal "996" work schedule (9 am – 9 pm, 6 days a week) common in some tech industries. While traditional open-source licenses like GPL v3 and Apache 2.0 govern how code can be used, modified, and distributed, the Anti-996 License introduces a unique human-rights layer that obligates users to comply with local labor standards. Understanding the difference between Anti-996 License and GPL/Apache licenses is crucial for developers choosing legal frameworks for their projects.

Primary Goals and Core Philosophy

Each license serves fundamentally different purposes in the open-source ecosystem.

Anti-996 License: Labor Rights Enforcement

The primary goal of the Anti-996 License is to enforce compliance with local labor-and-employment laws and forbid contractual clauses that restrict workers' rights. According to the LICENSE file in the 996icu/996.ICU repository, the license requires strict adherence to applicable labor standards in the user's jurisdiction.

GPL v3: Software Freedom Preservation

GPL v3 focuses on preserving the freedom to use, modify, and redistribute software while ensuring these freedoms pass downstream. It employs strong copyleft mechanisms to prevent proprietary forks, ensuring that any derivative work remains open source.

Apache 2.0: Permissive Commercial Use

Apache 2.0 provides a permissive grant of rights, including an explicit patent-license clause, while allowing proprietary reuse. It prioritizes commercial flexibility and legal safety for enterprises adopting open-source software.

Legal Requirements and Core Restrictions

The most significant difference between Anti-996 License and GPL/Apache licenses lies in their restrictive clauses.

Anti-996 Clause 2: Labor Law Compliance

In 996icu/996.ICU/blob/master/LICENSE, Clause 2 imposes a unique requirement:

2. The individual or the legal entity must strictly comply with all
   applicable laws, regulations, rules and standards of the jurisdiction
   relating to labor and employment where the individual is physically
   located … In case that the jurisdiction has no such laws … the
   individual … are required to comply with Core International Labor
   Standards.

This clause explicitly targets the "996" work schedule, making the license unenforceable for companies violating labor standards.

GPL v3: Copyleft Obligations

GPL v3 requires that any distributed derivative works be licensed under GPL v3 as well. As stated in Section 5 of the GNU GPL v3:

... you must cause any work that you distribute or publish, that in whole
or in part contains or is derived from the Program or any part thereof,
to be licensed as a whole at no charge to all third parties under the
terms of this License.

Apache 2.0: Attribution and Patent Grant

Apache 2.0 requires preservation of copyright notices and includes a patent-retaliation clause. Section 3 of the Apache License 2.0 states:

... grants you a perpetual, worldwide, non‑exclusive, no‑charge,
royalty‑free, irrevocable patent license … If you initiate patent
litigation … your patent licenses under this Agreement will terminate.

Copyleft vs. Permissive Classification

Understanding the technical classification of each license highlights their compatibility differences.

• Anti-996 License: Neither copyleft nor permissive in the traditional sense. Its enforceability hinges on labor-law compliance rather than code-level reciprocity. This unique positioning makes it incompatible with standard open-source definitions that prohibit discrimination against fields of endeavor.

• GPL v3: Strong copyleft. Any derivative work must be licensed under GPL v3, ensuring software freedom propagates downstream. This prevents proprietary incorporation of GPL-licensed code.

• Apache 2.0: Permissive. Downstream works may be released under any license, including proprietary ones. This flexibility makes Apache 2.0 popular for commercial open-source projects.

Enforcement Mechanisms and Patent Rights

The difference between Anti-996 License and GPL/Apache licenses extends to how violations are prosecuted and how patents are handled.

Enforcement Through Different Legal Frameworks

• Anti-996: Enforced through civil-law claims regarding labor-law violations rather than copyright infringement. A company using Anti-996 licensed code while enforcing a "996" work schedule could face action based on breach of the license's labor clauses.

• GPL v3: Enforced through copyright law. Violation constitutes copyright infringement, with remedies including injunctions and damages.

• Apache 2.0: Enforced through copyright law, with additional patent-related enforcement mechanisms.

Patent Grant Provisions

• Anti-996 License: Contains no explicit patent clause.
• GPL v3: Implicitly covers patents through its "no additional restrictions" language.
• Apache 2.0: Contains an explicit patent-grant clause that terminates if the user initiates patent litigation against the project.

License Compatibility Issues

The Anti-996 License presents unique compatibility challenges not seen with GPL or Apache licenses.

Because the Anti-996 License imposes labor-law requirements that restrict who can use the software (specifically excluding entities that violate labor standards), it is not compatible with most standard open-source licenses. Both GPL and Apache licenses prohibit discrimination against fields of endeavor and do not restrict usage based on the user's labor practices.

• GPL v3: Only compatible with other GPL-compatible licenses. Cannot be combined with Anti-996 code because the labor-law restrictions violate GPL's freedom principles.
• Apache 2.0: Compatible with a wide range of permissive licenses, but not with Anti-996 due to contradictory obligations regarding user restrictions.

Summary

• The Anti-996 License uniquely requires compliance with local labor laws and Core International Labor Standards, targeting the "996" work schedule through civil-law enforcement rather than copyright mechanisms.

• GPL v3 employs strong copyleft to ensure software freedom propagates downstream, enforced through copyright law with implicit patent protections.

• Apache 2.0 offers a permissive framework allowing proprietary reuse, featuring explicit patent grants and enforcement through standard copyright mechanisms.

• The Anti-996 License is incompatible with GPL and Apache licenses due to its labor-law restrictions, which violate the non-discrimination principles of traditional open-source definitions.

Frequently Asked Questions

Can I combine Anti-996 licensed code with GPL or Apache licensed code?

No, you cannot combine Anti-996 licensed code with GPL or Apache licensed code in the same project. The Anti-996 License imposes labor-law requirements that restrict who can use the software, which conflicts with the non-discrimination principles of both GPL and Apache licenses. GPL specifically prohibits additional restrictions that limit users' freedoms, while Apache 2.0 permits unrestricted use including commercial applications that might employ "996" work schedules.

What happens if a company uses Anti-996 licensed code while enforcing a "996" work schedule?

If a company uses software under the Anti-996 License while violating local labor laws or enforcing "996" work schedules (9 am – 9 pm, 6 days a week), they breach the license terms. Unlike GPL or Apache licenses where violations trigger copyright infringement claims, Anti-996 violations would likely be pursued through civil-law claims regarding labor-law violations. The company could lose their right to use the software and potentially face legal action based on the labor-law compliance clause in 996icu/996.ICU/blob/master/LICENSE lines 13-24.

Does the Anti-996 License provide patent protection like Apache 2.0?

No, the Anti-996 License does not contain an explicit patent grant clause like Apache 2.0. The Apache License 2.0 includes a specific provision granting users a perpetual, worldwide, non-exclusive patent license that terminates if the user initiates patent litigation. GPL v3 addresses patents implicitly through its "no additional restrictions" language. The Anti-996 License focuses exclusively on labor-law compliance and does not address intellectual property rights beyond standard copyright notices.

Why did the 996.ICU community create a new license instead of using GPL or Apache?

The 996.ICU community created the Anti-996 License because GPL and Apache licenses focus solely on software freedom and intellectual property rights without addressing labor rights. The "996" work schedule (9 am – 9 pm, 6 days a week) is illegal in many jurisdictions, yet standard open-source licenses allow any entity—including those violating labor laws—to use the software. The Anti-996 License adds a human-rights layer that prohibits use by entities that do not comply with local labor standards or Core International Labor Standards, making it a purpose-specific tool for protesting exploitative work practices.

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