playwright_stealth (original)

---

What playwright_stealth (original) actually does

The first Python port of the stealth evasions, and still the one a search for the package name is most likely to surface. Its evasion list reflects the browser surfaces of the period it was written in.

What playwright_stealth (original)'s maintenance signals mean

pushed_at reads 2024-07-29 — 746 days, or about 2.0 years, before the field check, which places it inside the 365-to-1095-day band the rubric calls NRND.

NRND is borrowed intact from the electronic component catalogues, where it means Not Recommended for New Designs, and it is the most useful state in this register precisely because it is not a synonym for broken. The part is still in the catalogue. You can still buy it. If you are designing something new, do not design it in. Applied here: what this project does, it very likely still does. Starting a new build on it means inheriting a maintenance gap you did not create and cannot close.

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 playwright_stealth (original) sits in this catalogue

playwright_stealth (original) 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: SeleniumBase (UC Mode) (ACTIVE), playwright_stealth (maintained fork) (SEMI), Botright (ACTIVE). 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 MIT, alongside the rest of the MIT entries in this register, and it sits with everything else currently marked NRND. 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.

This register records that playwright_stealth (maintained fork) supersedes playwright_stealth (original). Supersession here is declared, never inferred: it is printed only where a project or its author says so, because "newer" and "replaces" are not the same relation and treating them as one is how a list starts recommending rewrites nobody asked for.

The playwright_stealth (original) relations page sets every declared edge side by side on licence, push date, release cadence and derived state.

What to settle before you adopt playwright_stealth (original)

Popularity and maintenance are independent variables, and this entry is the clearest demonstration of that in the section. The maintained fork is listed beside it; compare their push dates before choosing.