How brodev3/antidetect works
Project type and purpose
• This is a Node.js console application (“Antidetect browser”) for creating and managing multiple virtual browser profiles with anti-detection/fingerprinting protection.
• It connects to a Google Sheets “Dashboard,” uses Google Drive for storage, and calls an external FingerprintSwitcher service to mask browser fingerprints.
File structure
Top-level:
• index.js – entry point, boots the console UI and orchestrates modules
• config.js / .env_example – configuration loader for Google API credentials and local/drive paths
• package.json – dependencies (googleapis, inquirer or similar console UI, request/http libs)
• LICENSE, README.md
app/
• commands.js – maps console commands (create, list, open, delete profiles)
• interfaces.js – defines the console UI menus and prompt flows
scr/ (scripts/core logic)
• browser.js – spawns browser processes (likely Puppeteer/Playwright or native browser) with fingerprint & proxy settings
• db.js – reads/writes profile meta from Google Sheets via Sheets API
• manage.js – high-level orchestration (create profile folder structure, tie together browser.js & fingerprint.js & db.js)
• fingerprint.js – fetches and applies fingerprint JSON from FingerprintSwitcher service
• utils.js – shared helpers (parsing, error handling, file‐system interactions)
engines/ – example engine templates, showing pluggable engine architecture for additional browser backends
README for additional insights
• Core features: profile creation, proxy setup, fingerprint masking (User-Agent, canvas, WebRTC), data isolation (local/cloud), Google-Sheets “Dashboard” as the data store, Google Drive sync for profile directories.
• External services: Google Sheets API, Google Drive API, FingerprintSwitcher API.
• Usage flow: user issues console commands → module loads credentials → reads/writes sheet → fetches fingerprint → spawns browser.
Be as detailed as possible
• How config.js propagates into each module that needs credentials or paths.
• “engines/” as a plugin registry feeding into browser.js.
• Don’t overthink—simply outline every logical component and its interactions to provide maximum clarity.