brave/brave-core

Core engine for the Brave browser for mobile and desktop. For issues https://github.com/brave/brave-browser/issues

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 37 minutes ago
Type:ApplicationCategory(s):Browsers & ExtensionsWeb Development
Added to GitGenius on September 19th, 2026
Created on November 10th, 2017
Open Issues & Pull Requests: 426 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 1,435
Total Stargazers: 3,602 (+0)
Total Subscribers: 123 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Brave Core is a customization layer for Chromium that powers the Brave browser across mobile and desktop platforms.

The project solves the problem of building a privacy-focused browser by providing a set of changes, APIs, and build scripts that modify Chromium without forking it entirely. It works by fetching and syncing Chromium source code at a specified branch version, then applying Brave-specific patches and integrations. The approach includes mounting brave-core at a designated location within the Chromium source tree and linking in specialized components like the adblock-rust engine through a foreign function interface.

Developers should choose this if they want to contribute to or build the Brave browser itself, or if they need to understand how a production browser customizes Chromium while maintaining synchronization with upstream changes. The project suits teams building privacy-centric browser variants or those studying how to maintain a large codebase of patches against a rapidly evolving upstream. The repository explicitly directs users to the separate brave-browser repository for issue tracking, releases, and wiki documentation, indicating a deliberate separation between the core engine code and user-facing project management.

The project maintains active coordination across multiple dependencies including Chromium, adblock-rust, and various platform-specific build configurations. Development requires platform-specific setup with dedicated wiki pages for Android, Linux, iOS, macOS, and Windows environments. The build process involves downloading tens of gigabytes of Chromium history, indicating substantial infrastructure investment in managing the dependency chain. Contributing guidelines and a security policy are formally documented, and the project maintains an active community presence through multiple channels including a Q&A community forum and translation coordination through a dedicated platform.