rebrowser-patches

---

What rebrowser-patches actually does

Patches Puppeteer and Playwright for the same CDP execution-context leak, and shipped with a written explanation of the mechanism that remains one of the clearer public accounts of why driven browsers are detectable at the protocol layer.

What rebrowser-patches's maintenance signals mean

pushed_at reads 2025-05-09 — 462 days, or just over a year, 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 rebrowser-patches sits in this catalogue

rebrowser-patches 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: Patchright (Node) (ACTIVE), Patchright (Python) (ACTIVE), CDP-Patches (ARCHIVED). 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.

Its licence field is empty, and this register treats that as a finding rather than a gap — see every entry here that declares no licence. Source you can read is not source you have been granted the right to use, modify or redistribute, and an absent licence file means exactly that absence and nothing friendlier. It is also grouped with everything else the rubric marks NRND.

This register records that Patchright (Node) supersedes rebrowser-patches. 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 rebrowser-patches relations page sets every declared edge side by side on licence, push date, release cadence and derived state.

What to settle before you adopt rebrowser-patches

The writeup has aged better than the code: read it for the mechanism, then check whether the patch set still applies to the driver version you use. It declares no licence, so reuse in a product is a question to answer first.