Undetected Python version of the Playwright testing and automation library.
1.4k
Stars
107
Forks
1
Open issues
4
Contributors
AI Analysis
Patchright is a patched version of Playwright that aims to evade bot detection while automating browser interactions. It serves web scraping, automation, and anti-detection use cases where standard Playwright would be blocked. This is specialized tooling for users operating at the intersection of web automation and anti-detection, not a general-purpose browser automation library.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Playwright fork optimized for anti-detection: Python port of undetected browser automation
Patchright-Python is a patched fork of Microsoft's Playwright designed to evade bot detection. It maintains API compatibility with Playwright while applying anti-detection modifications to the underlying browser drivers. Built for web scraping, account automation, and testing scenarios where detection evasion is required. Adoption appears concentrated in scraping and anti-detection communities; mainstream adoption likely limited by legal/ethical concerns and reliance on continuous maintenance against evolving detection mechanisms.
Patchright began as a TypeScript project (3,595 stars) in late 2023–early 2024, with the Python port launched November 2024. Created by Kaliiiiiiiiii-Vinyzu, who also maintains a Node.js variant. The project explicitly targets users who need Playwright's features without bot-detection triggers.
Python port accumulated 1,413 stars in ~8 months (as of July 2026), gaining 15 stars in the 7 days prior. Growth appears steady but modest relative to base Playwright (14,796 stars). Sponsorship from proxy providers (Swiftproxy, RapidProxy, NodeMaven, ColaProxy) suggests monetization and community investment, but also indicates the user base is concentrated in scraping/anti-detection segments rather than mainstream testing.
Adoption not verified by public case studies, company announcements, or quantified usage data in README. Proxy provider sponsorships imply commercial use, but evidence remains indirect. No metrics on deployed instances, PyPI download trends beyond the badge, or documented enterprise adoption provided in README. Community around similar tool (invisible_playwright, 1,676 stars) suggests a user base exists, but scale is unknown.
Appears to be a drop-in Playwright replacement that modifies browser driver binaries and detection signatures. README describes it as 'patched and undetected' but does not detail the specific patching methodology. Likely involves tampering with JavaScript API signatures, WebDriver detection, or Chrome DevTools Protocol headers. Exact implementation not verifiable from README alone.
README includes a badge for GitHub Actions CI/CD workflow (patchright_tests.yml), suggesting automated testing exists. However, test scope and coverage metrics are not documented in the README excerpt provided.
Last push 2026-07-05, one day before analysis date — active ongoing maintenance. Repository created November 2024, so ~20 months old. Consistent recent activity and badge updates indicate the maintainer is actively tracking changes. No evidence of stagnation; however, pace of star growth (~15/week) suggests modest rather than explosive traction.
ADOPT IF: you need Playwright's API surface but require active bot-detection evasion; you accept the maintenance burden of keeping a fork in sync with upstream Playwright; legal/ethical context of your use case permits it; you have the expertise to monitor detection-signature changes. AVOID IF: you need stable, vendor-supported long-term maintenance; you require legal indemnification; your use case does not inherently require evasion (vanilla Playwright is simpler); you need predictable, conservative API evolution. MONITOR IF: you are evaluating anti-detection solutions and need to track whether patchright maintains feature parity with Playwright; you are considering building detection-evasion into your product and want to measure community interest.
Independent dimensions
Mainstream potential
2/10
Technical importance
5/10
Adoption evidence
3/10
- Maintenance sustainability: Patchright must continuously patch against Playwright updates and evolving bot-detection mechanisms. Single-maintainer project with no documented backup. Fork drift could leave Python port lagging TypeScript parent or vanilla Playwright.
- Detection arms race: Anti-detection signatures decay as websites and anti-bot vendors evolve detection heuristics. Patchright's effectiveness requires active, reactive patching. No guarantee patches will keep pace.
- Legal/ethical ambiguity: Use cases are predominantly scraping and account automation, which may violate terms of service or local law depending on context. Users assume legal risk.
- Upstream breaking changes: Playwright API changes may require patchright adaptation. Large upstream changes could cause temporary incompatibility or force branching decisions.
- Sponsorship dependency: Reliance on proxy provider sponsorships may create alignment incentives with proxy adoption rather than pure tool quality. Limited documentation of governance or conflict-of-interest policies.
Patchright-Python likely to remain a specialized niche tool serving the anti-detection scraping community. Growth will be bounded by narrow use cases and the cat-and-mouse dynamic of evasion-detection cycles. Mainstream Playwright adoption will continue to dominate. If Playwright itself adds native anti-detection features, patchright's utility may erode. Alternatively, if detection pressure increases, demand could grow, but maintainability risks will grow proportionally.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Website
- https://pypi.org/p/patchright
- Language
- Python
- License
- Apache-2.0
- Last updated
- 5d ago
- Created
- 20mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open pull requests
No open pull requests.
Similar repos
Kaliiiiiiiiii-Vinyzu/patchright
Patchright is a patched fork of Playwright that aims to evade browser...
feder-cr/invisible_playwright
invisible_playwright is a modified Firefox browser with anti-detection patching...
CloakHQ/CloakBrowser
CloakBrowser is a stealth Chromium browser with source-level C++ fingerprint...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
1.4k | +6 | Python | 7/10 | 5d ago |
|
|
3.6k | — | TypeScript | 7/10 | 2w ago |
|
|
1.7k | — | Python | 8/10 | 4d ago |
|
|
14.8k | — | Python | 9/10 | 1w ago |
|
|
28k | — | Python | 8/10 | 15h ago |
|
|
1.4k | — | Python | 8/10 | 1w ago |
Official, widely trusted, mainstream testing/automation standard. Patchright explicitly designed as a compatible variant for detection-evasion use cases; not a replacement but a specialized alternative for contexts where detection matters.
Parent project with 2.5× higher stars. Python port trails by design (Python adoption in browser automation is large, but TypeScript/Node dominates this niche). Python port appears to be feature-parity effort rather than innovation lead.
Similar concept — Playwright fork for evasion. Comparable star count suggests patchright-python has achieved parity in ~8 months, but both remain niche projects relative to vanilla Playwright.
Integrates Playwright with Scrapy framework. Serves different use case (framework plugin vs. standalone anti-detection library); not directly competitive but overlaps in scraping automation.
Browser-level evasion tool with much higher adoption. Patchright is library-based; CloakBrowser is a full browser distribution. Different positioning but both address detection evasion.