How the Anti-996 License Handles Jurisdiction-Specific Labor Laws
The Anti-996 License defers to the strictest applicable labor laws in the user's jurisdiction rather than imposing universal rules, falling back to Core International Labor Standards when local regulations are absent.
The 996.ICU repository introduced the Anti-996 License to address exploitative work schedules in the tech industry. Unlike traditional open-source licenses that focus solely on software distribution, this license incorporates labor law compliance as a condition of use. Understanding how the license handles jurisdiction-specific labor laws is essential for developers and organizations adopting software under these terms.
The Jurisdiction-Aware Compliance Framework
The license text in LICENSE (lines 17-35) establishes a three-tiered approach to labor law compliance that adapts to the user's specific legal environment.
Section 2 - Deference to Local Labor Statutes
Section 2 of the license requires strict compliance with "all applicable laws, regulations, rules and standards of the jurisdiction relating to labor and employment." This applies based on:
- The individual's physical location
- The individual's birthplace or naturalization
- The legal entity's registration or operating location
The clause specifies "whichever is stricter," meaning users must adhere to the most protective standard among all applicable jurisdictions.
Fallback to Core International Labor Standards
When a jurisdiction lacks specific labor laws regarding work hours or overtime, Section 2 mandates compliance with Core International Labor Standards. This fallback ensures that even in regions with minimal worker protections, licensees must respect fundamental International Labour Organization (ILO) conventions regarding maximum working hours and overtime compensation.
Section 3 - Protection of Employee Rights
Section 3 explicitly prohibits any contract or agreement that attempts to waive or limit employees' rights as granted by the applicable labor laws. This provision operates independently of local enforceability—even if a jurisdiction permits "996" style contracts (9 AM to 9 PM, 6 days per week), the license itself voids such agreements for software distributed under its terms.
Implementing Jurisdiction-Specific Compliance
Organizations using Anti-996 licensed software must integrate compliance checks into their development and deployment workflows.
License Notice Requirements
Every redistributed file must include the full license header. The LICENSE file requires displaying the complete text unchanged on every copy:
/*
* Anti 996 License Version 1.0 (Draft)
* -------------------------------------------------
* © <year> <copyright holder>
*
* This work is licensed under the Anti‑996 License.
*
* You must:
* • Display the full license text unchanged on every copy.
* • Comply with all applicable labor‑law regulations of the
* jurisdiction where you or your organization operate
* (see Section 2 of the license).
*/
Automated Compliance Verification
Development teams can implement CI/CD checks to ensure license presence. The following Bash script verifies that the LICENSE file accompanies every commit:
#!/usr/bin/env bash
# ci/check-license.sh – run in CI pipeline
if ! git diff --cached --name-only | grep -q '^LICENSE$'; then
echo "ERROR: LICENSE file not staged. The Anti‑996 License requires the license to be included in every distribution."
exit 1
fi
Jurisdiction Detection and Hour Limits
Organizations can implement automated checks against local work-hour regulations. This Python example demonstrates mapping jurisdictions to maximum weekly hours:
import platform
import os
# Mapping of known jurisdictions → max weekly work hours (example)
MAX_HOURS = {
"CN": 44, # China
"US": 40, # United States (FLSA)
"EU": 48, # EU Working Time Directive
# ... add more as needed
}
def get_jurisdiction():
# Simple heuristic: read from env var set by deployment pipeline
return os.getenv("JURISDICTION", "UNKNOWN")
def check_overtime(weekly_hours):
juris = get_jurisdiction()
limit = MAX_HOURS.get(juris, 48) # fallback to core standard (48h)
if weekly_hours > limit:
raise RuntimeError(
f"Overtime violation: {weekly_hours}h > {limit}h allowed in {juris}. "
"Anti‑996 License requires compliance with local labor law."
)
Key Files in the 996.ICU Repository
The 996.ICU repository maintains several critical documents governing license terms:
LICENSE– Contains the full legal text of the Anti-996 License Version 1.0 (Draft), including Section 2 (jurisdiction-specific compliance) and Section 3 (employee rights protection). Located at the repository root.LICENSE_CN– Official Chinese translation of the license, ensuring accessibility for Chinese-speaking developers and organizations subject to Chinese labor law.README.md– Project overview that contextualizes the license within the broader 996.ICU movement against excessive working hours in the tech industry.
Summary
- The Anti-996 License defers to the strictest applicable labor laws in the user's jurisdiction rather than imposing universal work-hour limits.
- When local laws are absent, the license mandates compliance with Core International Labor Standards (ILO conventions).
- Section 3 explicitly voids any contract that attempts to waive labor rights, regardless of local enforceability.
- Compliance requires organizations to identify applicable jurisdictions, verify local statutes, and implement automated checks to prevent overtime violations.
- The license text resides in
LICENSEwith a Chinese translation available inLICENSE_CN.
Frequently Asked Questions
What happens if my country has no labor laws restricting work hours?
If your jurisdiction lacks specific statutes regarding work hours or overtime, the Anti-996 License requires you to comply with Core International Labor Standards. This fallback ensures adherence to fundamental ILO conventions regarding maximum working hours and rest periods, providing baseline protection even in regions without comprehensive local labor regulations.
Does the Anti-996 License override local employment contracts?
The license does not directly override local contracts in a legal sense, but it voids the software license for any entity that attempts to enforce contracts waiving labor rights. Section 3 explicitly prohibits agreements that limit employees' statutory rights as a condition of using the software. If an organization requires such waivers, they violate the license terms and lose rights to use, modify, or distribute the software.
How do I determine which jurisdiction applies to my use of the software?
According to Section 2 of the license, you must consider multiple factors: your physical location, your birthplace or naturalization, and for legal entities, your place of registration or operation. The license applies the "whichever is stricter" rule, meaning you must comply with the most protective labor standards among all jurisdictions that apply to you. Organizations should document their jurisdiction analysis as part of compliance documentation.
Is the Chinese version of the license legally equivalent to the English version?
The repository provides LICENSE_CN as an official Chinese translation to ensure accessibility, but the English version in LICENSE typically serves as the governing legal text unless explicitly stated otherwise. Users should treat the English version as authoritative for legal interpretation, while the Chinese translation aids understanding for Chinese-speaking developers. Both versions convey the same jurisdiction-specific compliance requirements outlined in Sections 2 and 3.
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:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →