HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
blueboxd
chromium-legacy
C++2021–2025
blueboxd / chromium-legacy

chromium-legacy

Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+

2Distinct people
22Mentions
0Explicit recommenders
451GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Latest Chromium (≒Chrome Canary/Stable) for Mac OS X 10.7+

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 year22 dated mentions

Observed mentions: 2021-02-05 18:00:33 UTC to 2025-08-21 16:25:09 UTC.

02462021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

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
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC707
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC716
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

What Hacker News says

22 sources
Ah, but note I said "mainstream browser engine", not "mainstream browser!" The mainstream browsers themselves dropped Mavericks some time ago, but other developers have been maintaining backports. Firefox Dynasty is actually a relatively recent development. For a while I was using Chromium Legacy[1], which, yes, did stop getting updated a little over a year ago. But then just in time, i3roly came along with Firefox Dynasty[2]! It's true that if i3roly drops Firefox Dynasty, and the Chromium Legacy developer doesn't return (there has been some movement on the repo), that will be the end of this project. But that could be many years from now! 1: https://github.com/blueboxd/chromium-legacy 2: https://github.com/i3roly/firefox-dynasty
In Show HN: OS X Mavericks Forever

Tell HN: Chromium forks for legacy platforms are disappearing from GitHub

This is really strange! Chromium Legacy is an up-to-date fork of Chromium which supports back to Mac OS X 10.7 Lion (from 2011). On Friday, the developer's Github account and all of his repositories suddenly disappeared. The links now return 404 errors. https://github.com/blueboxd/ https://github.com/blueboxd/chromium-legacy Today, the same thing happened to Supermium, an equivalent project for Windows which supports back to XP. To my knowledge, the developers of Chromium Legacy and Supermium are wholly unaffiliated. https://github.com/win32ss/ https://github.com/win32ss/supermium Does anyone happen to know what the heck is going on? It's a little scary and makes me not want to trust GitHub. I don't see anything relevant in GitHub's repository of DMCA notices[1], and I'm having trouble coming up with legal grounds on which such a takedown
Read the rest
could happen. --- 1: https://github.com/github/dmca
121 points · Open discussion
If the browser is properly sandboxed, and you're only accessing the internet through the browser, you should reasonably safe, no? Obviously it's better to have defense in depth, but I don't see the immediate danger. What is the attack vector you are concerned about? --- I daily drive a 2013-era version of OS X, using a similar modified version of Chromium[1] to browse the web. I'm pretty sure I've plugged the holes I need to plug in order to be reasonably safe, but if you have a specific concern I'd like to hear about it! 1: https://github.com/blueboxd/chromium-legacy
In Supermium – Chromium fork for Win 2003/XP and newer
Thanks, note that it's all very much built on the shoulders of giants! For example, the "Chromium Legacy Downloader" just adds automatic updates (and some tweaks) to to an existing project. Chromium Legacy itself—a branch of Chromium kept in sync with upstream which retains support for legacy OS X—is maintained by a Japanese developer I don't know much about. https://github.com/blueboxd/chromium-legacy. Other downloads, like the Dolphin emulator, are basically just source recompiles, which use MacPorts tooling to support legacy OS X. MacPorts has incredible legacy support.
In Projects for Old Versions of OS X

Showing the 15 most recent of 22 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.