Mullvad Browser

---

What Mullvad Browser actually does

Tor Browser's hardening without the Tor network attached: the same goal of making every user of the build present identical readings, with the network path left entirely to you.

What Mullvad Browser's maintenance signals mean

The liveness field here is pushed_at, read as 2026-07-23 against a field check 22 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.

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 Mullvad Browser sits in this catalogue

Mullvad Browser 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: ungoogled-chromium (ACTIVE), Brave Browser (ACTIVE), Tor Browser (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.

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

Substitutes for the same job, with no claim that either is better: Brave Browser, Camoufox, LibreWolf, Tor Browser. The alternative relation is symmetric and carries no ranking, because this register publishes no ranking of any kind. The full Mullvad Browser comparison table sets all of them side by side on licence, push date, release cadence and state.

What to settle before you adopt Mullvad Browser

Uniformity only protects you inside a crowd, and this build's crowd is necessarily smaller than the one it inherited its defences from. The licence field is also worth resolving before you package it for anyone else.