patchright-enhanced README

The project's README from github.com/whaleyxbt/patchright-enhanced. As one markdown file: README.md.

patchright-enhanced

stealth browser automation framework for penetration testing, scraping, and WAF bypass. Built on Patchright.

clean chrome sessions that pass Cloudflare, Kasada, DataDome, and other WAFs out of the box.

that's basically just a wrapper around OG patchright, so it's easier to get started.

Setup for Linux

# Install dependencies
npm install

# Install Chrome for Patchright
npx patchright install chrome

# Copy env template and configure
cp .env.example .env

# Add your proxies
# Format: host:port:username:password (one per line)
nano proxies.txt

Configuration

All settings are in .env:

Variable Default Description
BROWSER_EXECUTABLE_PATH /usr/bin/google-chrome-stable Path to Chrome binary
BROWSER_TIMEZONE Europe/Berlin Browser timezone
MAX_PARALLEL 1 Number of parallel sessions
START_PAGE_URL https://google.com/ Initial page to open

Usage

npm run build
npm start

it opens a chrome session with the configured proxy and navigates to START_PAGE_URL. the session stays open until you close the browser window manually.

Anti-Detection

my small framework relies entirely on patchright's built-in stealth patches:

patchright-enhanced (whaleyxbt/patchright-enhanced)

Searching Database…

What is this?It's a stealth browser automation toolkit built on top of Patchright (a patched Playwright) aimed at QA testing, monitoring, scraping, and penetration testing. It focuses on producing clean Chrome sessions that get past WAFs like Cloudflare, Kasada, and DataDome out of the box.
Is this a standalone tool, or more of a wrapper around something else?It's essentially a thin wrapper around the original Patchright library with extra configuration and workflow conveniences layered on top, which the author says makes it easier to get started than using raw Patchright.
How do I get it running?Follow the Linux setup steps in the README, then configure the .env file (Chrome binary path, timezone, parallel session count, and the start page URL) before launching it.
Do I need Chrome installed separately?Yes — by default it expects Google Chrome at /usr/bin/google-chrome-stable; you can point BROWSER_EXECUTABLE_PATH to a different binary if yours lives elsewhere.
Does it guarantee bypassing WAFs like Cloudflare?The README only claims sessions 'pass Cloudflare, Kasada, DataDome, and other WAFs out of the box' without guaranteeing it, and it adds no fingerprint spoofing of its own — it relies entirely on whatever Patchright's built-in stealth patches already cover.
Does this run on Windows or macOS too, or just Linux?The README only documents setup for Linux, so Windows/macOS aren't covered — treat it as Linux-first unless you test it yourself elsewhere.
What anti-detection tricks does it rely on?It leans fully on Patchright's stealth patches: the Runtime.enable leak is patched, --disable-blink-features=AutomationControlled is added, --enable-automation is removed, and navigator.webdriver natively returns false, with no extra fingerprint spoofing layered on top.
Can I run multiple browser sessions at once?Yes, the MAX_PARALLEL setting in .env controls how many sessions run concurrently, and it defaults to 1.
Does the browser close itself when done?No, the session stays open until you manually close the browser window; it doesn't auto-terminate after navigating to the start page.
What tech stack is this built with?It's a Node.js/TypeScript project built directly on the Patchright library, which itself is a stealth-patched fork of Playwright.
Creator
whaleyxbt
Size
0.1 MB
Stars
498
Updated
CommitOct 10
Age
6mo
Commits · 90 Days