Botright

---

What Botright actually does

A Playwright-based framework that bundles captcha handling with stealth configuration, so the browser setup and the challenge response are one dependency rather than two.

What Botright's maintenance signals mean

The liveness field here is pushed_at, read as 2026-07-15 against a field check 30 days later. That is inside 90 days, and 90 days is where the second edition of the rubric put ACTIVE after moving it down from the first edition's 180.

The reason for the move is worth stating, because it is the kind of threshold that looks arbitrary until you know what it is measuring against: detection changes on a shorter cycle than half a year, so a six-month-old evasion is not a current one. What a recent push does not tell you is what was in it. A commit landing on a branch is not a release, not a fix, and not a test — it is evidence that somebody is still there.

No release was captured for this entry, which this register records as unknown rather than as none. The distinction matters more than it looks: a project with no tags and a project whose tags the sweep failed to read produce the same blank cell, and printing them as the same fact would be the register asserting something it has not measured.

Where Botright sits in this catalogue

Botright is filed in section 02, automation stealth plugins, patches & cdp-leak fixes, whose scope is this: Patches and plugins for Puppeteer, Playwright and Selenium, plus the proxies and cursor libraries that sit beside them. An entry sits in exactly one section here. Where a project could defensibly go in two, it is placed where a reader would look for it first rather than where it fits most tidily, and that is an editorial decision rather than a measured one.

Filed beside it in the same section: playwright_stealth (maintained fork) (SEMI), playwright_stealth (original) (NRND), Selenium-Driverless (NRND). Comparing an entry against its own section-mates is more informative than comparing it against the catalogue as a whole, because everything in a section is answering roughly the same question and the differences left over are the ones that matter.

It is published under GPL-3.0, alongside the rest of the GPL-3.0 entries in this register, and it sits with everything else currently marked ACTIVE. Read those two facets together: a permissively licensed project that stopped shipping is not a safer dependency than a copyleft one that did not, and a filter on one axis alone will tell you the wrong thing.

What to settle before you adopt Botright

Bundling couples your evasion surface to a captcha-solving implementation's own lifecycle. Under GPL-3.0, also settle the distribution question before it becomes part of a shipped product.