hcaptcha-challenger

---

What hcaptcha-challenger actually does

Uses multimodal models to answer image challenges, and is the clearest public example of the shift in captcha solving from hand-built classifiers to general models prompted at the challenge.

What hcaptcha-challenger's maintenance signals mean

pushed_at reads 2026-01-28, which is 198 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.

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 hcaptcha-challenger sits in this catalogue

hcaptcha-challenger 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: BrowserForge (SEMI), fingerprint-suite (Apify) (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 GPL-3.0, alongside the rest of the GPL-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.

What to settle before you adopt hcaptcha-challenger

Model-based solving carries per-call cost and latency that a classifier did not, so the economics differ from what older tooling taught. GPL-3.0 and the model provider's own terms are both part of the decision.