nodriver

---

What nodriver actually does

The same author's replacement approach: drop webdriver entirely and speak CDP directly, which removes the driver binary as a component that can be fingerprinted at all.

What nodriver's maintenance signals mean

pushed_at reads 2026-05-13, which is 93 days before the field check and therefore inside the 90-to-365-day band this rubric calls SEMI. SEMI is the first edition's ACTIVE bucket after it was split in two, and the split exists because a quarter of silence in this field is a fact worth printing rather than absorbing.

A SEMI entry is not a warning and not a recommendation. It is a request to look: open the commit history and see whether the gap is a maintainer between jobs, a project that has reached a stable shape and stopped needing changes, or an abandonment that has not yet crossed a threshold. All three produce the same field value, and this register cannot tell them apart — it can only make sure you know the gap is there.

There is no tagged release at all — not an uncaptured one, but none published. That is a real fact about how the project is consumed: without a tag, depending on it means depending on a branch, and a branch is a moving target. This register keeps no_releases as a field separate from a null release tag for exactly that reason, because "none exists" and "the sweep did not read one" are different claims.

Where nodriver sits in this catalogue

nodriver 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: CDP-Patches (ARCHIVED), undetected-chromedriver (NRND), SeleniumBase (UC Mode) (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 AGPL-3.0, alongside the rest of the AGPL-3.0 entries in this register, and it sits with everything else currently marked SEMI. 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.

nodriver is recorded as superseding undetected-chromedriver. Both directions of that edge are stored once and reversed at build time, so the graph cannot contradict itself — an entry cannot supersede something that does not record being superseded by it.

Substitutes for the same job, with no claim that either is better: Patchright (Python), Selenium-Driverless, SeleniumBase (UC Mode). The alternative relation is symmetric and carries no ranking, because this register publishes no ranking of any kind. The full nodriver comparison table sets all of them side by side on licence, push date, release cadence and state.

What to settle before you adopt nodriver

Dropping the driver also drops the Selenium API surface, so this is a migration rather than an upgrade. Budget for rewriting selectors and waits, not for swapping an import.