HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
brave
brave-browser
Web Development2018–2026
brave / brave-browser

brave-browser

Brave browser for Android, iOS, Linux, macOS, Windows.

Web DevelopmentSystems & InfrastructureMobile & Desktop
Explore on GitHubRead Hacker News discussions
145Distinct people
203Mentions
1Explicit recommenders
24.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Brave browser for Android, iOS, Linux, macOS, Windows.

GitHub

Where it is used

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

What people are saying

edit2: Nevermind all this, Brave did in fact implement protected content this earlier this year https://github.com/brave/brave-browser/issues/413 I still can't use brave to…

dkhenry used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 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 year203 dated mentions

Observed mentions: 2018-06-21 03:22:42 UTC to 2026-09-28 20:15:01 UTC.

0102030402018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 30 mentions; 0 submissions, 30 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 31 mentions; 6 submissions, 25 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 43 mentions; 2 submissions, 41 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 32 mentions; 2 submissions, 30 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 22 mentions; 2 submissions, 20 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 13 mentions; 2 submissions, 11 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 10 mentions; 1 submissions, 9 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
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC11011
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC30030
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC31625
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC43241
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC32230
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC22220
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC13211
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC11011
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC1019

From the project README

An excerpt from the repository, fetched Nov 12, 2026.

Read the project’s introduction
Brave Browser This repository is not needed for building the browser and only holds issues, releases and the wiki. The source code and contributions are at https://github.com/brave/brave-core. You can visit our website to get the latest stable release. Resources Issues: Bug reports and feature requests for the Brave Browser. Releases: Releases of Brave Browser hosted on GitHub. See Brave Release Schedule for more information. Wiki: Documentation for developers, administrators, and power users. User-facing documentation is available at the Brave help center. Documentation and guides: Additional technical information, primarily for developers. Contributing Please see the contributing guidelines. To get started building Brave, hop over to the Wiki. Security Policy Please see the security policy. Community Join the Q&A community if you'd like to get more involved with Brave. You can ask for help, discuss features you'd like to see, and a lot more. We'd love to have your help so that we can continue improving Brave. You can also ask questions and interact in the community-guest channel on Brave Software's Slack. Help us translate Brave to your language by submitting translations at https://explore.transifex.com/brave/brave_en/. Follow @brave on X for important news and announcements.
Read the full README on GitHub

What Hacker News says

43 sources
annoyingnoob·Dec 15, 2021
> do not send data to third-parties and do not work as a monetization strategy for low-quality content publishers Oh, yeah? They may aggregate or otherwise anonymize data but there is absolutely reporting to advertisers. https://github.com/brave/brave-browser/wiki/Security-and-pri... They call it 'ad confirmations' and spend a lot of time trying to convince you that its all private. Its not all private to Brave itself, which is an advertising network.
In Preventing Pool-Party Attacks
jonathansampson·Dec 6, 2021
Brave isn't a mere superset of Chromium. We actually remove, modify, and proxy quite a bit. You can read the nitty-gritty details at https://github.com/brave/brave-browser/wiki/Deviations-from-.... You absolutely could create a similar browsing experience (with excellent extensions like uBlock Origin), but you're still ultimately at the mercy of the browser vendor. For example, uBlock Origin is facing pressure from forthcoming Manifest V3 changes which threaten the existence of the extension (and many others like it). Brave, as a Browser, has committed itself to continuing support for these types of extensions. One of the other large elements of Brave is Brave Ads & Rewards, and the ability for users to anonymously translate their attention into substantive support for content creators in a privacy-preserving fashion. Sampson (Brave Team)
In Goodbye Brave
concinds·Dec 6, 2021
Firefox is less secure, as has been said many times here already. You might dislike the Blink hegemony but they're the only ones who invest enough in security. Vivaldi's closed source, and Firefox doesn't have site isolation on all platforms yet. (Neither does Safari). Chrome had it in 2018. 3 years is not excusable when a 0day can be the difference between freedom and jail (or worse). "Privacy" is defective when your exploit mitigation is deficient. You've got a lot worse privacy when your whole computer is owned, than when a few websites track which other websites you've been to. None of this is new. https://news.ycombinator.com/item?id=27219402 Brave has a top-notch team, uses Blink, and has some of the best fingerprinting protection I've seen in any browser, much better than Safari, and better than Firefox. They have good people worki
Read the rest
ng on it. The fact that an attempt to improve privacy [0] is being used to bring Brave bad PR is ironic. [0]: https://github.com/brave/brave-browser/wiki/Deviations-from-...
In Goodbye Brave
supernes·Dec 2, 2021
I appreciate what Brave are doing, but this will affect them whether they support MV2 or not. Extensions on most Chromium forks are installed through Google's Chrome Web Store, so when Google drops support browsers who do not agree will need an alternative distribution platform (like Opera's fork). More generally, Brave's attitude towards Chromium changes has been "disable first, ask questions later", even when it hurts forward-looking developers and useful feature adoption [1]. In the case of the file system API, there's also a possible conflict of interest, given how they're pushing IPFS and the rest of the crypto web bullshit. My biggest gripe with them is that most of their development efforts go into developing the cryptocurrency features and they end up neglecting general browser usability and innovation. [1] https://github.com/brav
Read the rest
e/brave-browser/issues/11407
In Chrome phasing out Manifest v2 support from Jan 2022
ildon·Dec 1, 2021
Yes, many are refusing to implement it due to security concerns. A notable one is Brave, which is based on Chromium, and yet refuses to enable it (https://github.com/brave/brave-browser/issues/11407). I'm skeptical that reducing access to the FS actually protects users. Those that would be fooled by scams based on FileSystemAccess APIs would very likely be fooled also with other less intricate tactics. So I doubt that the overall security of users is in practice affected. At least, browsers that refuse to implement the FileSystemAccess APIs could implement them, but leave them disabled by default, and require some non-trivial action to enable them. So users with a very basic understanding of how things work in the browser would not be able to enable them.
In SQLite in a PWA (Anita) with FileSystemAccessAPI

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