Core engine for the Brave browser for Android, Linux, macOS, Windows. For issues (by brave)

Brave-core Alternatives

Similar projects and alternatives to brave-core

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better brave-core alternative or higher similarity.

Suggest an alternative to brave-core

Reviews and mentions

Posts with mentions or reviews of brave-core. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-20.
  • Randomly got this in the mail
    1 project | | 27 Nov 2021
    Since Brave is completely FOSS (under the MPL 2.0) and the source code of the browser is publicly available, I challenge you to find a single thing proving your baseless claims. I will wait.
  • Best part about using Brave...bigger than earning BAT
    1 project | | 23 Nov 2021
    According to, if you, for example, block that domain using your hosts file or firewall, it seems like Tor will autodisable. According to, you can also disable it via Group Policy (Windows Pro and up only).
  • Should I use Brave or Vivaldi? I value both privacy and low resource usage.
    2 projects | | 20 Nov 2021
    What do you think I should use as a source instead? An article written by a third party? Why not the developers themselves? If you would have at least read the blog post I linked to (which you probably didn't), you know that there are tools like mitmproxy, Fiddler and others that you can use to verify if Brave transmits any PII to their servers (spoiler: no). You can even read the source code, since Brave is FOSS.
  • Introducing Brave Wallet: The First Secure Wallet Built Natively in a Web3 Crypto Browser. No Extension Required.
    1 project | | 17 Nov 2021
  • Another reason to make the switch
    1 project | | 17 Nov 2021
  • Is Brave Browser being infiltrated already?
    2 projects | | 13 Nov 2021
    and I found this one: which resolves
  • PSA: about the Android Brave app crash
    2 projects | | 8 Nov 2021
    According to and its corresponding pull request the issue was very likely due to an addition of a P3A probe to detect default search engine settings in Brave.
  • Brave Browser is broken.
    1 project | | 7 Nov 2021
    Commit log available here (you can start at 1.31.90 and work back to 1.31.87):
  • FileSystemAccess API flag was re-added to Nightly.
    1 project | | 4 Nov 2021
    If someone is interested, the flag to enable the FileSystemAccess API to the nightly build 1.33.51 3 days ago.
  • New Brave Wallet enabled by default on Brave Nightly 🔥
    2 projects | | 20 Oct 2021
    Brave Wallet’s source code is available under an Open Source license, unlike other popular web 3 extensions.
  • Used CSS to apply a background to Firefox but isn't the same as expected
    1 project | | 20 Oct 2021
    @-moz-document url(about:newtab), url(about:home) { body.activity-stream { background-image: url("") !important; background-size: cover; background-position: center bottom; } }
  • Please verify your recovery phrase.
    1 project | | 9 Oct 2021
  • Since when is Vivaldi sending X-Client-Data?
    2 projects | | 5 Oct 2021
    I seem to remember checking on this last year and Vivaldi wasnt sending X-Client-Data to Youtube. Today its there. Looking at Brave they got the same issue where it was fine last year, but popped up 12 months later and was finally manually patched (
  • Over 800MB of unclearable documents and data in iOS version
    1 project | | 4 Oct 2021
    There have been more than one issue which have the symptom of taking up space and they have occurred at different times. Each incident requires investigation. The one you linked to was fixed with
  • Brave and Firefox to intercept links that force-open in Microsoft Edge
    4 projects | | 4 Oct 2021
    Great write-up! I did want to share a brief response to the following, however:

    > The new implementations in Brave and Firefox follow the exact parsing logic I wrote for EdgeDeflector. It’s not the only way to parse them, it’s not the best way to parse them, but it’s the way every third-party implementation now parses them. Neither codebases attribute the code to EdgeDeflector, although both are clearly inspired by it. (Don’t get me wrong, I’m fine with this.)

    With all due respect to the author, I don't believe this is an accurate statement. While the problem being solved (parsing a microsoft-edge: protocol string) is quite simple, there are still noticeable differences in how EdgeDeflector, Brave, and Firefox have chosen to tackle this process.

    [EdgeDeflector]( checks to see not only that the string begins with "microsoft-edge:", but also that it does not contain any space character (" "). The latter check *is not* conducted by [Brave]( or [Firefox]( EdgeDeflector performs an initial case-insensitive check for the protocol, while Brave and Firefox do not (both expect lower-case characters). There is a code path in EdgeDeflector where a case-sensitive check may also be conducted.

    EdgeDeflector and Brave both remove the "microsoft-edge:" prefix from the input, but Brave performs and additional check at this point. If the resulting string is empty, Brave stops attempting to extract a workable URL.

    EdgeDeflector performs no such empty-string test, instead proceeding to check whether the resulting string starts with "https://" or "http://" (a case-insensitive match). Firefox also proceeds to check whether the string starts with "https:" or "http:". Brave, on the other hand, proceeds to check whether the resulting string starts with a ? character.

    If the string doesn't start with a ? character, Brave attempts to parse the string as a URL and initiate navigation. If the string begins with a ? character, Brave removes that character and proceeds to split the string into chunks on occurrences of the & character.

    With the string split into chunks, Brave cycles over each piece looking for one that starts with "url=". If a match is found, Brave attempts to parse everything after the = character as a URL. If it succeeds, that URL is visited.

    Firefox and EdgeDeflector do take a similar approach in these later steps. While EdgeDeflector utilizes .NET's HttpUtility.ParseQueryString to parse and extract the URL value, Firefox passes the string to the URLSearchParams constructor, and retrieves the "url" parameter from the resulting object. Brave is the odd-man out on this step, opting instead to split the string, and cycle through to the nearest matching chunk.

    While there are similarities here and there (given the simplicity of the task itself), there are stark differences as well. One thing is certain, however, Brave and Firefox both explicitly refer to EdgeDeflector as leading this effort to restore liberty to users impacted by Microsoft's heavy-handed approach to shoehorning users back into Microsoft Edge.


Basic brave-core repo stats
5 days ago

brave/brave-core is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.

SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
Find remote C++ jobs at our new job board There is 1 new remote job listed recently.
Are you hiring? Post a new remote job listing for free.