996.ICU is not a software project. It is a GitHub-native labor-rights protest, a media event, a community archive, and a licensing experiment wrapped in one repository. The name comes from the line “work by 996, sick in ICU”: a criticism of the 9 a.m. to 9 p.m., six days per week work schedule that became associated with parts of China’s technology industry.

That distinction matters for ghtrends. A normal repo page asks what the tool does, how to install it, and whether it is worth adopting. 996.ICU asks a different set of questions: why did a labor issue become one of GitHub’s most-starred repositories, what did the repo actually ask people to do, and how should readers interpret it years after the first viral wave?

The README is direct about the project’s boundaries. It says there is no official account, app, or merchandise except the official domain and this repository. It says 996.ICU is not a political movement, that it upholds labor law, and that it asks employers to respect legitimate employee rights and interests. It also says the project welcomes positive and constructive proposals and mature speech. Those lines are part of the project identity, not footnotes.

What The Repository Contains

The README explains the 996 schedule, links to press coverage, lists actions supporters can take, quotes public reactions, states principles, points to translations, lists related community projects, explains why issues were disabled, and links the Anti 996 License.

The action list is small but revealing. It asks people to update a list with evidence, add a badge to support the project, license projects with the Anti 996 License, add proposals, and go home at 6 p.m. without feeling sorry. This is not a roadmap for a software product. It is a participation script for a protest.

The community section links adjacent repos such as 955.WLB, 996.LIST, 996.Leave, 996.Petition, support.996.ICU, 996.Blockchain, and 996.Error. Some of those projects are active historical artifacts now, not current operational systems. They show how fast a GitHub issue spread into lists, badges, license drafts, petitions, browser extensions, and cultural references.

The README also states that issues were switched off because the issue area was out of control. That is a maintenance fact and a cultural signal. A repo that receives this much attention can stop being a manageable collaboration surface.

No Install Step

There is no install command. The repo is mostly Markdown, license text, lists, translations, proposals, badges, and related materials. If you want to support it as a developer, the README’s concrete actions are to link the official site, add the badge, use or study the Anti 996 License, contribute evidence to the lists, translate content carefully, or participate through related projects.

Do not treat the repo as an npm package, Python library, browser extension, or deployable app. Some related repos tried those shapes, such as recruitment-site tagging or company lists, but 996.ICU itself is the central symbolic repository.

The Anti 996 License

The license file begins with "Anti 996" License Version 1.0 (Draft). It is adapted from the MIT license, but adds labor-law conditions. The key idea is that users of licensed work must comply with labor and employment laws, and must not induce, suggest, or force employees or contractors to waive or weaken labor-related rights and remedies.

This is the repo’s most unusual technical contribution. It tries to connect source-code licensing with labor conditions. Whether that is enforceable, compatible with a project’s distribution needs, or accepted by downstream users is a legal and governance question. Developers should not treat it as interchangeable with MIT, Apache-2.0, GPL, or Creative Commons licenses.

The GitHub API reports the license as Other, which is expected for a custom draft license. In frontmatter, this page records it as Anti-996 because that is the project-facing license name.

Maintenance And Current State

The repo is not archived. It was pushed on 2025-08-22 and had 276,274 stars and 20,828 forks as of 2026-06. Those numbers are enormous, but the meaning differs from a tool repo. Stars mostly measure the original wave of support, bookmarking, and symbolic alignment. Forks can reflect translation, archival interest, mirrored materials, or attempts to contribute.

There is no latest release, which is normal here. Recent open PRs as of 2026 include an update to the LICENSE copyright holder information, AI/employment commentary, supporter additions, a Korean translation, README typo fixes, blacklist description updates, and language-link additions. That suggests light historical maintenance, not active product development.

Issues are disabled. The README says this was a personal decision because even with interaction limits on, the issue area was totally out of control. So raw issue count in the repo data should not be used the way one would use issues for a software package.

How To Read The Star Count

996.ICU is one of the clearest examples of GitHub stars as social signal. A developer can star a compiler, framework, tutorial, protest repo, or joke repo with the same button. The number means attention, but attention has different causes.

For 996.ICU, the star count should be read as the scale of a public developer reaction to working-hour culture, not as adoption of code. This matters because many top GitHub rankings mix tools, curricula, lists, protests, and memes. Ranking alone does not tell you what a repository is.

It is still worth writing as a repo page because searchers want to know what happened, what the Anti 996 License means, why issues are closed, whether the project is official, and whether it still matters. The README answers many of those directly, but not in a compact evaluation format.

Project Stars as of 2026-06 Language License field Role
996.ICU 276,274 Markdown Anti 996 License draft Central labor-rights protest and license experiment
955.WLB 36,243 Markdown null in API List of work-life-balanced companies
996_list 855 Vue MIT Company list and discussion around 996 and 955
996-icu-avengers/Natasha 535 JavaScript NOASSERTION Recruitment-site tagging around 996ICU and 955WLB lists
996.petition 277 Markdown null in API Petition-oriented related project

The comparison shows a pattern: 996.ICU is the focal point, while related repos explored lists, petitions, browser tooling, and work-life-balance alternatives. Many are small compared with the main repo, but they help explain why the original repository became more than a README.

What It Is Not

It is not a live labor-law database. It is not a verified legal resource. It is not a software package. It is not an official account system. It is not a replacement for labor counsel or local law.

It is also not a normal open-source license recommendation. The Anti 996 License has a political and legal purpose, and the README describes it as a draft adapted from MIT. If a project wants to use it, maintainers should evaluate compatibility, enforceability, and downstream acceptance with care.

For another high-star repository that is mostly content rather than installable software, compare jwasham/coding-interview-university. For the broader awesome-list culture, sindresorhus/awesome is the reference point. For a directory whose curation is practical rather than protest-driven, awesome-selfhosted is a useful contrast.

FAQ

What does 996.ICU mean?

It means “work by 996, sick in ICU.” The README defines 996 as working 9 a.m. to 9 p.m., six days per week, and frames ICU as the health consequence of that schedule.

Is 996.ICU a software project?

No. It is primarily a Markdown repository for a labor-rights initiative, related lists, translations, badges, proposals, press links, and the Anti 996 License.

Why are issues disabled?

The README says the issue area was totally out of control even with interaction limits, so issues were switched off by the maintainer.

Is there an official app or merchandise?

The README says there is no other official account, app, or merchandise except the official domain and this repository.

What is the Anti 996 License?

It is a draft license adapted from MIT that adds labor-law compliance conditions. It should be evaluated as a custom labor-rights license, not as a standard permissive open-source license.

Is 996.ICU still active?

It is not archived and had recent PRs and a 2025 push, but it is no longer a fast-moving product project. Its current value is mainly historical, symbolic, and licensing-related.