You've already forked brave-origin-unlocker
mirror of
https://github.com/ObjectAscended/brave-origin-unlocker.git
synced 2026-06-21 12:42:34 +00:00
Angelo Trotta
63 lines
2.3 KiB
Markdown
63 lines
2.3 KiB
Markdown
# Brave Origin Unlocker
|
|
|
|
A TypeScript utility for unlocking Brave Origin features on Windows and macOS by modifying the local application state.
|
|
|
|
## Overview
|
|
|
|
This tool modifies the Brave Origin browser's local state configuration to unlock premium features. It works by updating the `Local State` JSON file used by Brave to store user preferences and license validation status.
|
|
|
|
## Features
|
|
|
|
- ✅ Unlocks Brave Origin features
|
|
- ✅ Modifies purchase validation state
|
|
- ✅ Updates SKU credentials
|
|
- ✅ Windows and macOS path compatibility
|
|
- ✅ Easy execution via Deno tasks
|
|
|
|
## Requirements
|
|
|
|
- **Deno** - Modern JavaScript/TypeScript runtime
|
|
- **Windows OS or macOS** - Supported operating systems
|
|
- **Brave Origin** - The browser being modified
|
|
- **File Write Permissions** - Access to browser configurations
|
|
|
|
## Installation
|
|
|
|
1. Install [Deno](https://deno.land/) if you haven't already.
|
|
2. Clone this repository:
|
|
```bash
|
|
git clone https://github.com/ObjectAscended/brave-origin-windows-unlocker.git
|
|
cd brave-origin-windows-unlocker
|
|
```
|
|
|
|
## How to Run 🚀
|
|
|
|
You can run the unlocker directly using the pre-configured Deno tasks:
|
|
|
|
### For Windows 🪟
|
|
```bash
|
|
deno task unlock-win
|
|
```
|
|
|
|
### For macOS 🍎
|
|
```bash
|
|
deno task unlock-mac
|
|
```
|
|
|
|
---
|
|
|
|
## Pre-Bundled Deno Binaries 🎉
|
|
|
|
In our latest releases, we offer **pre-bundled Deno binaries** that make running the unlocker easier than ever! 🚀 You can download them from our [latest release page](https://github.com/ObjectAscended/brave-origin-windows-unlocker/releases/latest). These binaries ensure a smooth setup and save you time.
|
|
|
|
## Why Run the Unlocker Natively? 🤔
|
|
|
|
Running the unlocker natively is typically a better choice than running a browser inside virtual/emulated environments. Here's why:
|
|
|
|
1. **Performance**: The native experience generally offers better performance than emulated environments. ⚡
|
|
2. **Simplicity**: You avoid complex setups and configurations, making it more straightforward for users of all levels. 🛠️
|
|
3. **Compatibility**: Some features and functionalities might only work seamlessly in a native environment, ensuring you get the most out of your tools. 🔗
|
|
4. **User Experience**: Enjoy a more intuitive interface and fewer problems managing dependencies. 😊
|
|
|
|
Enjoy using our tool! 🎈
|