hazetunnel

---

What hazetunnel actually does

A man-in-the-middle proxy that rewrites passing traffic to mask signals that mark it as non-organic, operating below the browser rather than inside it.

What hazetunnel's maintenance signals mean

pushed_at reads 2024-07-15 — 760 days, or about 2.1 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 hazetunnel sits in this catalogue

hazetunnel 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: FlareSolverr (ACTIVE), CloudflareBypassForScraping (ACTIVE), ghost-cursor (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.

What to settle before you adopt hazetunnel

Anything terminating TLS in the middle of your traffic is a security decision as much as a detection one — know what certificate your clients are trusting. Weigh that against how long it has been since the project last moved.