CDP-Patches

---

What CDP-Patches actually does

Takes a different route to the same problem: instead of patching the protocol, it moves the mouse and types through the operating system's own input layer, so the events arrive at the browser indistinguishable in origin from a person's.

What CDP-Patches's maintenance signals mean

archived reads true, set 2025-09-28. This is the only measured field in the rubric that outranks every date rule, and it outranks them for a good reason: every other signal here is the register inferring intent from behaviour, while this one is the maintainer stating intent directly. When the two disagree, the statement wins.

An archived repository is readable, forkable and permanently frozen. Nothing will be merged into it, and no advisory affecting it will be answered there. That makes it a reference rather than a dependency — genuinely valuable as the former, and a liability as the latter. The last push date is still printed above, because the interval between the last commit and the archive flag is itself informative about how the project ended.

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 CDP-Patches sits in this catalogue

CDP-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 (Python) (ACTIVE), rebrowser-patches (NRND), undetected-chromedriver (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.

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 ARCHIVED.

What to settle before you adopt CDP-Patches

OS-level input is platform-specific by construction, so what works on one target platform tells you nothing about another. The repository is archived, which is the maintainer's own statement and outranks every date rule in the rubric.