Skip to content

Latest commit

 

History

History
188 lines (138 loc) · 6.2 KB

README.md

File metadata and controls

188 lines (138 loc) · 6.2 KB

THREATBROWSER

A powerful, user-friendly browser designed for multi-accounting.

license last-commit repo-top-language repo-language-count

Developed with the software and tools below.

electronbuilder Prettier HTML5 YAML Vite Axios Vue.js
ESLint Electron Puppeteer TypeScript Vuetify JSON

🔗 Quick Links

📍 Overview

ThreatBrowser is the first open-source multiaccounting browser. Proxy integration, unlimited profiles, everything included.

📷 Gallery

  • Profiles Section Main

  • Bypassing fingerprint tests Main

  • Proxy Manager Main

📦 Features

  • Unlimited profiles
  • SOCKS4/5, HTTP/S proxy integration
  • Custom User Agents settings
  • Open-Source

🚀 Getting Started

Requirements

Ensure you have the following dependencies installed on your system:

  • Node.js: version 14.x or higher
  • npm: version 6.x or higher
  • TypeScript: version 4.x or higher
  • Electron: version 13.x or higher

⚙️ Installation for development

  1. Clone the threatbrowser repository:
git clone https://github.com/syrex1013/threatbrowser
  1. Change to the project directory:
cd threatbrowser
  1. Install the dependencies:
npm install

🤖 Running threatbrowser for development

Use the following command to run development build

npm run dev

🛠 Building for windows

Use the following command to build ThreatBrowser for windows

npm run build:win

You can also use prebuilt versions from our releses section.

🛠 Project Roadmap

  • ► Custom useragents
  • ► More customizations of profile
  • ► Exporting profiles and cookies
    and more!

🤝 Contributing

Contributions are welcome! Here are several ways you can contribute:

Contributing Guidelines
  1. Fork the Repository: Start by forking the project repository to your GitHub account.
  2. Clone Locally: Clone the forked repository to your local machine using a Git client. 
    git clone https://github.com/syrex1013/threatbrowser
  3. Create a New Branch: Always work on a new branch, giving it a descriptive name. 
    git checkout -b new-feature-x
  4. Make Your Changes: Develop and test your changes locally.
  5. Commit Your Changes: Commit with a clear message describing your updates. 
    git commit -m 'Implemented new feature x.'
  6. Push to GitHub: Push the changes to your forked repository. 
    git push origin new-feature-x
  7. Submit a Pull Request: Create a PR against the original project repository. Clearly describe the changes and their motivations.

Once your PR is reviewed and approved, it will be merged into the main branch.

📄 License

This project is protected under the MIT License. For more details, refer to the LICENSE file.

👏 Acknowledgments

Return