Open-source project
OnionBrowser/OnionBrowser avatar
OnionBrowser/OnionBrowser

Onion Browser reaches Tor through Orbot iOS, and its README spends 191 lines on credits

An open-source, privacy-enhancing web browser for iOS, utilizing the Tor anonymity network

2,713 stars548 forksSwiftNOASSERTION

At a glance

What is it?
This iOS browser sends traffic through Tor by way of a separate application, and the repository documents the browser itself in about twenty lines. What the file does cover is two admissions about traffic that used to reach the network another way, three branches live at once, and a license story the metadata and the file disagree about.
Who is it for?
Anyone reading this repository to judge Onion Browser's privacy properties will find the Tor implementation is not here; it lives in Orbot iOS, and the terms a redistributor needs live in the LICENSE file rather than in the metadata field. The version numbers agree with the release history, the default branch is being worked on, and two of the three live branches have no stated policy about fixes.
Can I use it commercially?
Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
Is it still maintained?
Yes. The repository last received commits 3 days ago.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • OnionBrowser/OnionBrowser2,713 ★ · +23
Star history
Repository2026-09-292026-11-15
OnionBrowser/OnionBrowser2.7k2.7k

23 Stars in the last 47 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The Tor path runs through Orbot iOS, not through this repository

Onion Browser encrypts and tunnels web traffic through the Tor network for iPhone and iPad, and the sentence that makes that claim names a second project as the thing doing the work: Orbot iOS. The 3.X feature list repeats the same dependency when it introduces its own headline items, saying the features are new to Onion Browser mostly by leaning on Orbot iOS. Read strictly, this repository supplies the interface, the WKWebView rendering engine, the bridge between an iOS application and a local proxy client, and the settings that decide what leaves the device. The circuit that traffic rides on belongs to a separate application, which means there is no Tor implementation in this tree to read. Anyone trying to work out what this browser can or cannot expose by reading Swift files here will reach the wrong answer, because the answer sits in whatever Orbot does while the tunnel is up and in whatever it does when it is not.

Finally and now mark the traffic gaps this branch closed

Two lines in the feature list read as admissions rather than announcements. One says that finally all traffic, including audio and video streams, is tunneled through Tor. Another says everything is downloadable now, including web pages. The adverb finally implies that earlier builds let some traffic reach the network outside the tunnel, and now implies the same thing about downloads. Media streams and saved pages are the two cases named explicitly, which tells a reader that before this branch shipped, a video element or a save could have arrived without going through Tor at all. What the list does not do is date either change. It carries no version numbers, so nothing in this file says which release closed the audio and video gap or which one widened downloads to any file type. The changelog linked below carries that mapping, and it is fetched from a raw URL pinned to the 3.X branch rather than to a tag, so what it shows is the head of that branch rather than a frozen release.

The README points outward for build steps, help, and release history

Measure the file by where its lines go. The navigation strip at the top resolves to the official site, a help wiki hosted on GitHub, the releases page, a donate page, and a raw changelog. Below that sits one paragraph on what the browser is, a line telling readers to open the LICENSE file for usage and redistribution terms, and a single bullet giving the version number. Then come five feature bullets and 38 language headings with contributor handles under each of them. Build instructions appear nowhere in the text; the section headed How to build yourself is one sentence naming BUILD.md. Nothing here describes the settings, the error states, or what the interface does when the tunnel is down. Documentation for four separate things sits outside this file, and the wiki link in particular is a surface that can drift from the code without leaving a trace in the repository.

Three branches stay live while the copyright line stops at 2024

Three long lived branches are reachable at once and the opening note links two of them. The default branch is 3.X, and that note says the older versions of Onion Browser can be found on 2.X and on 1.X. Nothing says which of the three receives fixes, and nothing marks 2.X or 1.X as frozen or unsupported, so a reader cannot tell from this file whether the older lines still receive security work. The release history shows three recent tags, all on 3.X: v3.4.0 published on 24 June 2026, v3.4.1 on 11 August 2026, and v3.4.2 on 1 October 2026. The last push to the default branch is dated 25 September 2026, just ahead of the newest tag, so the two dates agree about how current the work is. Against them sits the copyright line under the title, which still reads 2012 to 2024, Tigas Ventures, LLC. A visitor checking whether the project is current finds two dates that disagree, and the older one is the one printed first.

BUILD.md and Config.xcconfig hold what the Xcode project does not

The eighteen top level entries describe an iOS application assembled by Xcode rather than installed by a script:

text
.bartycrouch.toml
.gitignore
.weblate
BUILD.md
CHANGELOG.md
Config.xcconfig
LICENSE
OnionBrowser Tests/
OnionBrowser.xcodeproj/
OnionBrowser/
Podfile
Podfile.lock
README.md
Resources/
SECURITY.md
build-util/
fastlane/
misc/

Source sits under OnionBrowser and assets under Resources, with the test target in OnionBrowser Tests and the release automation in fastlane. Two entries deserve attention before anyone tries to compile anything. BUILD.md is the only place build instructions exist, and Config.xcconfig sits at the repository root precisely so its values are not buried inside project settings where a reader would not think to look. Because Podfile.lock is committed next to the Podfile, the dependency versions a given checkout resolves are pinned in the tree, so a build does not silently pick up newer pods than the ones already recorded. SECURITY.md is present for disclosure handling and .weblate for translation hosting.

Metadata reports NOASSERTION while a LICENSE file sits at the root

Two facts about licensing sit next to each other and do not line up. The repository's license metadata field reads NOASSERTION, which is what tooling records when no license could be identified from the files it examined. Meanwhile a LICENSE file sits at the repository root, and the opening text sends readers to it for usage and redistribution terms. That combination is worth recording without trying to resolve it. The terms a builder actually has to follow live in the file. The missing machine readable identifier means package indexes and automated license checks will treat this project as unlicensed, which is a different statement from the project having no license at all. Anyone planning to fork, redistribute, or ship a build of this browser should open LICENSE and read it directly, and should not take the metadata field as the answer in either direction.

The translation credits repeat names and one heading drops its colon

The longest part of the file is the acknowledgement list, 191 names spread across 38 language groups, and it has two habits worth noting. Names recur across groups, which is ordinary for a translator working in more than one language, but one handle appears twice inside a single group, in Chinese (Simplified), and others recur between neighbouring variants such as Portuguese (Brazil) and Portuguese (Portugal), or between Chinese (Simplified) and Chinese (Traditional). Six languages list exactly one contributor each, and the Croatian entry is the only heading written without a colon after the language name, which breaks the shape every other group follows. Nothing in the list names a maintainer per language, so a translator looking for where to send a correction has no route stated in this file other than the wiki link at the top.

Editorial conclusion

Anyone reading this repository to judge Onion Browser's privacy properties will find the Tor implementation is not here; it lives in Orbot iOS, and the terms a redistributor needs live in the LICENSE file rather than in the metadata field. The version numbers agree with the release history, the default branch is being worked on, and two of the three live branches have no stated policy about fixes. Read the wiki and BUILD.md directly, treat the metadata license field as absent rather than as permissive, and decide on the basis of which application actually builds the circuit you would depend on.

Frequently asked questions

Is there an Android version of Onion Browser?

No build in this repository targets Android. Onion Browser describes itself as a free browser for iPhone and iPad, and the top level holds an Xcode project, a Podfile, a fastlane directory, and BUILD.md rather than a cross platform build.

What does Onion Browser say about running it on an iPhone?

The opening description calls it a free web browser for iPhone and iPad that encrypts and tunnels web traffic through the Tor network with the help of Orbot iOS. Usage steps are not in the file; it points to a help wiki and the official site.

Which application carries Onion Browser's traffic?

Orbot iOS does. The 3.X feature list introduces its headline items as new to Onion Browser but mostly by leaning on Orbot iOS, so the browser supplies the interface, the WKWebView engine, and the settings, while the circuit itself comes from the other application.

What license governs Onion Browser?

The repository metadata reports NOASSERTION, so no machine readable license identifier was resolved. A LICENSE file sits at the repository root and the opening text points readers there for usage and redistribution terms, which makes the file the place to read and the metadata field no answer at all.

How current is the Onion Browser 3.X branch?

The last push to the default branch is dated 25 September 2026, and three releases shipped on that line: v3.4.0 on 24 June 2026, v3.4.1 on 11 August 2026, and v3.4.2 on 1 October 2026. The version printed in the README, 3.4.2, matches the newest tag.

Official sources

  1. Issues
  2. OnionBrowser/OnionBrowser on GitHub
  3. Project website
  4. README
  5. Releases
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/onionbrowser-onionbrowser.svg)](https://hysenlabs.com/projects/onionbrowser-onionbrowser)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/onionbrowser-onionbrowser.svg)](https://hysenlabs.com/projects/onionbrowser-onionbrowser)

Was this useful?