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:59: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

13 sources
jtnguyen·Dec 27, 2024Submission

Show HN: Plotcode – Infrastructure as Code patterns that you can copy and deploy

Hey HN Wanted to share my recent side project. I found it was a pain having to navigate through multiple places to find relevant patterns or snippets of code for AWS CDK and Pulumi. Thought why not combine patterns across multiple cloud providers into one place with search and filter. The most interesting part of the project was trying to optimise the site for mobile and lower-end devices. Came across the concept of "adaptive loading"[1] from Google and Facebook (2019). The current implementation is naive but the site renders a virtualized list or the entire list based on the number of logical processors detected. It's a very basic proxy for performance but is also not reliable. For example, the Brave browser reports a false number of logical processors to avoid telemetry[2]. Was wondering if anyone had any thoughts or experience with thi
Read the rest
s? Open to suggestions or feedback! Tech: Frontend - Nextjs 15 hosted on Cloudflare pages as a static site. Backend - Patterns are primarily sourced from the AWS CDK[3] and Pulumi[4] example repos. [1] https://web.dev/articles/adaptive-loading-cds-2019 [2] https://github.com/brave/brave-browser/issues/10808 [3] https://github.com/aws-samples/serverless-patterns [4] https://github.com/pulumi/examples
2 points · Open discussion
pavon·Oct 11, 2024
AFAIK, Microsoft is disabling manifest V2 extensions in Edge following the same timeline as Chrome[1]. Brave is continuing to run V2 extensions, but has no plan to stand up their own extension store[2], so it isn't clear how users will get the extensions, beyond a few handpicked ones that Brave is supporting[3]. [1] https://learn.microsoft.com/en-us/microsoft-edge/extensions-... [2] https://github.com/brave/brave-browser/issues/15187 [3] https://github.com/brave/brave-browser/issues/28367
In "Begin disabling installed extensions still using Manifest V2 in Chrome stable"
codedokode·Aug 30, 2024
I observed Firefox sending ECH extension in ClientHello, maybe I just enabled it in the settings, so Firefox supports ECH (on by default since version 119). However, virtually no servers support ECH now. Not Google, not Hackernews, not Cloudflare etc. This seems to be a not very good comparison, and it looks like it cherry-picks convenient for a certain browser points and ignores others. Look at "fingerprint protection", for example, and see that it does not include features that provide most fingerprinting data: - preventing reading GPU name via WebGL debugging extension (does Brave block this?) - preventing reading back canvas data which is used to fingerprint browser and OS code responsible for rendering graphics and text - enumerating audio devices And if you read the issues in Brave github [1], then you'll notice that Brave developer
Read the rest
s refuse to block features providing important fingerprinting information under compatibility" reasons (including GPU vendor and model), although these features could be made blocked only in high security mode. So regarding fingerprinting, the comparison you refer to is pretty much worthless: it doesn't mention many important fingerprinting APIs. [1] https://github.com/brave/brave-browser/issues/35646
In Chrome is entrenching third-party cookies that will mislead users
bsclifton·Feb 23, 2024
Something I would like to mention, as a dev on Brave, is that patches are considered a last resort. If there are patches, we try to keep them lightweight - like patch to have Chromium create the Brave version of the object (something we can restrict to one line). What you'll notice more often is a folder we have called `chromium_src`. This directory mirrors the directory structure for Chromium under `src` and the build system will look for matches. If there's a file with the same name under `chromium_src`, it'll prefer that one. That file then does what it needs to differently and then includes the original file. This approach helps keep things much more lightweight - but it has challenges too. If code fails to apply (file that `chromium_src` is matching gets renamed, etc) it can be hard to detect. This is where you'd want to have a test
Read the rest
to catch that. Another person shared - but here's a link to our patching documentation: https://github.com/brave/brave-browser/wiki/Patching-Chromiu... You'll notice the actual patching itself is introduced with the caveat: > When other options are exhausted, you can patch the code directly
In Brave's AI assistant now integrates with PDFs and Google Drive

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.