CloakBrowser

What CloakBrowser actually does

A Chromium-based anti-detect browser published in two builds — one free, one gated behind a licence key — with the gated build carrying the features the project positions as its differentiators.

What CloakBrowser's maintenance signals mean

The liveness field here is latest_release.published_at, standing in because the sweep did not capture a push date, read as 2026-08-11 against a field check 3 days later. That is inside 90 days, and 90 days is where the second edition of the rubric put ACTIVE after moving it down from the first edition's 180.

The reason for the move is worth stating, because it is the kind of threshold that looks arbitrary until you know what it is measuring against: detection changes on a shorter cycle than half a year, so a six-month-old evasion is not a current one. What a recent push does not tell you is what was in it. A commit landing on a branch is not a release, not a fix, and not a test — it is evidence that somebody is still there.

The release field is a second and different signal. chromium-v150…-pro was published 2026-08-11, and the gap between that date and the push date above is the interval in which work exists but has not been cut into anything you can pin a dependency to. A project that pushes constantly and tags rarely and a project that does the reverse look very different to anyone trying to depend on either.

Where CloakBrowser sits in this catalogue

CloakBrowser is filed in section 01, open-source anti-detect browsers & forks, whose scope is this: Browsers whose source you can read: anti-detect Firefox and Chromium forks, hardened builds, and the profile managers built on top of 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: LibreWolf (ACTIVE), arkenfox/user.js (ACTIVE), ShardBrowser (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 ACTIVE. 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 CloakBrowser

The register flags this entry for star velocity, which is two measured numbers and one note rather than an accusation: go and read the contributor graph and the release history yourself. Establish which capabilities live only in the gated build before you evaluate the free one.