HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
996icu
996.ICU
Developer Tools2019–2026
996icu / 996.ICU

996.ICU

Repo for counting stars and contributing. Press F to pay respect to glorious developers.

37Distinct people
38Mentions
0Explicit recommenders
277.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Repo for counting stars and contributing. Press F to pay respect to glorious developers.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 6:28:55 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year38 dated mentions

Observed mentions: 2019-03-27 04:28:30 UTC to 2026-09-12 13:02:37 UTC.

01020302019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 26 mentions; 9 submissions, 17 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC26917
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC202
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC716
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC000
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC202

What Hacker News says

26 sources
The "Anti 996 Licence" (see https://en.wikipedia.org/wiki/996_working_hour_system and https://github.com/996icu/996.ICU/blob/master/LICENSE ) has caused me to re-think what it means to say that a license is "for freedom." For example, a software license could support freedom to unionize. The GPL does not. I've decided to strictly use "software freedom", in order to avoid confusion with the much broader topic of "freedom". (BTW, many 'source available' licenses support your right to modify and run your software, if that's really all you want. Free software also includes the right to redistribute the software, including with modifications and in commercial sales, and without needing additional permissions from the original copyright owners.)
In Why Open Source Misses the Point of Free Software (2007)

Re-thinking open source license?

1. there are more and more discussions about open source license, one major one is whether cloud providers can just use the open source software to get tons of money without paying to the main contributor. 2. recently another interesting thing is many chinese engineers are proposing a license to not allow companies that force engineers to work long hours over time (this is happening a lot in China) to use the open source softwares https://github.com/996icu/996.ICU/blob/master/LICENSE I feel there are something common behind these things is it a time to re-thinking open source license?
4 points · Open discussion
So uh I did the current draft license in the repo, which is meant to be an additional restriction for whatever license a project is originally supposed to use. The idea I mean to show is that to exclude 996-type practice, you should use a more general definition that involves a work week and consecutive hours at work. There is no consideration on whether it will work: bad actors who violate labor laws tend to not care about FOSS licensing either. History tells us unionization and strikes would work better, but again recent Chinese news tells us with those you end up in a jail. Feasibility aside, I was dumb enough to not include something that says you gotta keep the restriction in modified version. https://github.com/996icu/996.ICU/pull/24748 is a fix that should get merged soon. There's also a notes on use section, which basically says:
Read the rest
1. It would not be GPL compatible because it adds an restrictions. Use it on more permissive licenses like MIT. 2. If you do use it, consider dual-licensing with GPL or AGPL so more people can potentially use it. Corps that do care about legal stuff don't like GPL anyways.
In Ask HN: Will software license be feasible for labor protection?
lnyng·Mar 30, 2019Submission

Ask HN: Will software license be feasible for labor protection?

Recently a Github repo [0] that shows resentment towards the long work hours (996 style, or 9am-9pm, 6 days a week) in Chinese tech companies is gaining popularity quickly among Chinese programmers. There is a discussion in the repo [1] (in Chinese) suggesting designing a new clause to existing software licenses for labor protection. For example, (from one of the post) > the source code is not permitted to use at 996ICU style work environment. The idea is that, if popular open source projects adopt this clause in their licenses, the work environment in China and maybe other countries will be improved. I guess it can be more specific about "996ICU" or specify average weekly work hours limit etc. But the question is, how feasible will such license clause be? Will there be any insurmountable limitation that makes it useless in practice? [0]
Read the rest
3 points · Open discussion

Showing the 15 most recent of 26 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.