996.ICU Movement
The 996.ICU movement succeeded as a consciousness-raising tool and put developer labor rights on the global agenda. The Anti-996 License is a legitimate choice for maintainers who want their code to discourage overtime exploitation. However, the repo itself is mostly a landing page—real work happens in the blacklist folder and the separate license repo. Reach for this if you want to signal solidarity or avoid licensing code to 996 companies; skip if you expect a production-ready enforcement mechanism—the license has never been tested in court.
The 996 Culture Developers Wanted to Push Back On
Chinese tech companies had normalized 996 schedules with minimal legal accountability, and developers had no coordinated way to identify exploitative employers or push back through their own ecosystem. The open source community had no licensing or tooling mechanism that took a stance on labor practices, leaving this gap entirely unfilled until this repo went viral.
A Star-Collection Hub, License, and Blacklist
The 996.ICU repository is the public face of a movement against China's 996 work culture. It houses a star-collection hub, links to the Anti-996 License (a modified MIT license that blocks use by companies violating labor laws), a community-maintained company blacklist, and solidarity badges developers can add to their projects.
How a March 2019 Backlash Went Global
The movement exploded in March 2019 after Chinese tech executives publicly defended 996 culture, triggering backlash. Press coverage from Financial Times, Wired, and RadiiChina amplified it globally. Guido van Rossum (Python creator) publicly called 996 inhumane. The sheer scale—276k stars—made it impossible to ignore, and it inspired a whole ecosystem of related repos (whitelists, petition tools, blockchain evidence stores).
The Anti-996 License, Badge, and Blacklist Explained
- ✓Star-collection hub that drove the movement to GitHub's trending page
- ✓Anti-996 License (adapted from MIT) that explicitly prohibits use by companies violating labor laws
- ✓Company blacklist with user-submitted evidence of 996 practices
- ✓Solidarity badge (996.ICU badge) you can embed in any project's README
- ✓Rich ecosystem: 955.WLB whitelist, 996.Leave overseas job guide, 996.Petition, and more
- ✓Cross-references press coverage and public statements from tech executives like Jack Ma and Richard Liu
What the Movement Actually Achieved
- ✓Enormous reach: 276k stars brought developer labor rights into mainstream tech conversation
- ✓Practical licensing option: the Anti-996 License gives maintainers a concrete way to take a stance
- ✓Spawned a whole ecosystem: 955.WLB, 996.Leave, 996.Petition, and other spin-off projects extend the movement's reach
- ✓Backed by Python creator Guido van Rossum calling 996 inhumane—credibility from the open source mainstream
- ✓State media (Xinhua) published articles critical of 996, partly validating the movement's goals
- ✓Provides a company blacklist with evidence so developers can make informed career decisions
Where the Anti-996 License Falls Short
- △The Anti-996 License has never been tested in court—enforceability against large corporations is entirely untested
- △The issues section was shut down by the repo owner due to spam, reducing community dialogue
- △Blacklist entries vary in evidence quality—no formal verification process for submissions
- △The repo is mostly a hub—actual license development happens in a separate repo (kattgu7/996-License-Draft)
- △The movement raised awareness but did not produce direct legal or regulatory change for affected workers
Adding the Badge, Checking a Company's Reputation
- •Adding the 996.ICU badge to your open source project to signal labor rights solidarity
- •Researching a company's overtime reputation before accepting a job offer in China
- •Licensing your project under the Anti-996 License to discourage exploitative employers
- •Contributing evidence to the blacklist to warn other developers
- •Exploring related repos like 955.WLB (whitelist of work-life balanced companies) for job hunting
Submitting Blacklist Evidence or Relicensing Your Project
Fork the repo to submit blacklist entries with verifiable evidence (news articles, court records, employee testimonials). To add the solidarity badge to your project, copy the markdown snippet from externals/instruction.md. If you're a maintainer, consider relicensing under the Anti-996 License. For general browsing, the README and linked 996.icu website cover the full context.
No Install — Fork, Read, Contribute
No installation required. This is a GitHub repository—clone it, read the README, and follow the contribution guides for the blacklist or badge instructions.
955.WLB, 996.Leave, and the Real License Repo
Who Should Add the Badge or Browse the Blacklist
Use this repo if you want to add a solidarity badge to your projects, contribute to the blacklist, or license code under the Anti-996 License. Browse it if you're job-hunting at Chinese tech companies and want to check a company's overtime reputation. Skip it if you need a legally battle-tested license or direct legal recourse—the 996.ICU repo raises awareness, but doesn't litigate.
Questions About the Movement and License
It stands for 'Work by 996, sick in ICU'—an ironic phrase among Chinese developers implying that sustained 996 overtime (9am–9pm, 6 days a week, 60+ hours) can literally land you in the intensive care unit.
An open source license adapted from MIT that explicitly prohibits companies violating labor laws from using software under it. It's maintained in a separate repo (kattgu7/996-License-Draft) but linked from 996.ICU.
Community members submit evidence—court rulings, news articles, employee testimonials—via pull requests to the blacklist folder. No formal verification process exists, so evidence quality varies.
No—it functions as a solidarity signal, not a technical restriction. Developers add it to READMEs to show support for labor rights. Enforcement depends on the Anti-996 License, which itself has never been tested in court.
The repo owner disabled issues personally due to overwhelming spam, not GitHub. Community discussion shifted to Slack and other channels linked in the README.