HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
t3dotgg
vsc-material-but-i-wont-sue-you
TypeScript2025–2025
t3dotgg / vsc-material-but-i-wont-sue-you

vsc-material-but-i-wont-sue-you

The original owner of the Material UI theme for VS Code is grumpy, so I made a version you are safe to use as you please :)

Explore on GitHubRead Hacker News discussions
5Distinct people
6Mentions
0Explicit recommenders
721GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The original owner of the Material UI theme for VS Code is grumpy, so I made a version you are safe to use as you please :)

GitHub

Where it is used

No documented product use has been verified yet.

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 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM 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 day6 dated mentions

Observed mentions: 2025-02-26 03:57:13 UTC to 2025-03-16 02:40:23 UTC.

0123452025-02-26 00:00:00 UTC to 2025-02-27 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 commentsFeb 262025-02-27 00:00:00 UTC to 2025-02-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-28 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-03-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-02 00:00:00 UTC to 2025-03-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-03 00:00:00 UTC to 2025-03-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-04 00:00:00 UTC to 2025-03-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-05 00:00:00 UTC to 2025-03-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-06 00:00:00 UTC to 2025-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-07 00:00:00 UTC to 2025-03-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 72025-03-08 00:00:00 UTC to 2025-03-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-09 00:00:00 UTC to 2025-03-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-10 00:00:00 UTC to 2025-03-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-11 00:00:00 UTC to 2025-03-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-12 00:00:00 UTC to 2025-03-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-13 00:00:00 UTC to 2025-03-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-14 00:00:00 UTC to 2025-03-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-15 00:00:00 UTC to 2025-03-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-16 00:00:00 UTC to 2025-03-17 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 16

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
Feb 262025-02-26 00:00:00 UTC2025-02-27 00:00:00 UTC505
Feb 272025-02-27 00:00:00 UTC2025-02-28 00:00:00 UTC000
Feb 282025-02-28 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 12025-03-01 00:00:00 UTC2025-03-02 00:00:00 UTC000
Mar 22025-03-02 00:00:00 UTC2025-03-03 00:00:00 UTC000
Mar 32025-03-03 00:00:00 UTC2025-03-04 00:00:00 UTC000
Mar 42025-03-04 00:00:00 UTC2025-03-05 00:00:00 UTC000
Mar 52025-03-05 00:00:00 UTC2025-03-06 00:00:00 UTC000
Mar 62025-03-06 00:00:00 UTC2025-03-07 00:00:00 UTC000
Mar 72025-03-07 00:00:00 UTC2025-03-08 00:00:00 UTC000
Mar 82025-03-08 00:00:00 UTC2025-03-09 00:00:00 UTC000
Mar 92025-03-09 00:00:00 UTC2025-03-10 00:00:00 UTC000
Mar 102025-03-10 00:00:00 UTC2025-03-11 00:00:00 UTC000
Mar 112025-03-11 00:00:00 UTC2025-03-12 00:00:00 UTC000
Mar 122025-03-12 00:00:00 UTC2025-03-13 00:00:00 UTC000
Mar 132025-03-13 00:00:00 UTC2025-03-14 00:00:00 UTC000
Mar 142025-03-14 00:00:00 UTC2025-03-15 00:00:00 UTC000
Mar 152025-03-15 00:00:00 UTC2025-03-16 00:00:00 UTC000
Mar 162025-03-16 00:00:00 UTC2025-03-17 00:00:00 UTC101

What Hacker News says

6 sources
soraminazuki·Mar 16, 2025
It's worth noting the code is illegally relicensed without permission from copyright holders. The author is acting in bad faith. https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you Also, > obfuscated code which spawns child processes to download data for unnecessary reasons https://github.com/microsoft/vsmarketplace/issues/1168#issue... No one in the right mind would expect a theme to do this. Its only purpose is to provide static data to the editor.
In Microsoft apologizes for removing VSCode Material Theme extension
theobr·Feb 26, 2025
Hey y'all, I made the most prominent fork of this extension "Material Theme (But I Won't Sue You)" The maintainer went off the deep end last year. He pulled the (originally apache 2) source offline, then started threatening to sue people for hosting alternative versions, including them in other IDEs, etc. Genuine lunatic. Out of an abundance of precaution, I've taken the following action on my fork: 1. I have the VS Code team auditing it as we speak, and I've given them full permission to immediately pull it from the marketplace & force uninstall it from users if they find ANYTHING malicious. 2. I have audited the code base thoroughly (nothing seemed malicious) 3. I have removed ALL code related to changelogs, analytics, Open Collective and html rendering. The only thing that seemed slightly concerning was the html + sanity loader for cha
Read the rest
ngelogs, so I gutted it entirely. Two PRs removed almost all the deps and over 7,000loc (mostly package-lock) Repo is here if anyone else would like to audit https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you
In Material Theme has been pulled from VS Code's marketplace
oefrha·Feb 26, 2025
The original author seemed to talk a lot about funding development/maintenance, so I got curious about what the hell needs to be maintained. I cloned the https://github.com/t3dotgg/vsc-material-but-i-wont-sue-you repo and had a look. Here's a LoC summary: =============================================================================== Language Files Lines Code Comments Blanks =============================================================================== CSS 2 142 119 0 23 TypeScript 32 2026 1650 243 133 ------------------------------------------------------------------------------- HTML 2 59 49 1 9 |- JavaScript
Read the rest
2 2 2 0 0 (Total) 61 51 1 9 =============================================================================== Total 36 2227 1818 244 165 =============================================================================== Among those, 622 lines of TS are hex color definitions for variants in scripts/generator/settings/specific. Most of the rest seems pretty boilerplatey, e.g. look at the 599 lines in scripts/generator/color-set.ts. So the question remains: what the hell is there to maintain (that takes more than a couple minutes every $godknowshowlong)? I've published and maintained waaaaay more substantial open source projects for years without expectation of any financial contribution.
In Material Theme has been pulled from VS Code's marketplace

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.