Hush blocks cookie nags and refuses to block ads
🤫 Noiseless Browsing – Content Blocker for Safari
At a glance
- What is it?
- A Safari content blocker with one release from December 2020 and commits through July 2026, where the privacy claim rests on being a host of rules rather than a proxy, the app refuses to accept cookies and refuses to block ads on purpose, its own code is MIT while the bundled rules are CC BY 3.0, and the UI test suite is pinned to one simulator name.
- Who is it for?
- Hush is the right choice if you are annoyed by consent dialogs rather than by advertising, because that is the whole scope and the app says so instead of expanding it. Two things to know first.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 112 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.
Star history
- oblador/hush3,726 ★ · +22
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| oblador/hush | 3.7k | 3.7k |
22 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One release in December 2020, commits through July 2026
The release list holds a single tag, v1.0, published 2020-12-23. The last commit to the default branch is dated 2026-07-26, so five and a half years of development sit on a branch with no second tag. The most prominent item on the page is an endorsement rather than a feature, and it is dated too: John Gruber of Daring Fireball, on 23 January 2021, recommending Hush to anyone who uses Safari. That is the freshest third-party signal the project has, and it is six months older than its first release. Nothing about the page claims the app is actively developed, and the app store listing is the only artefact a user is pointed at, so the version a visitor gets is whatever the single 1.0 tag produced.
It blocks nags and tracking, and refuses ads on purpose
The scope is narrower than the word content blocker usually implies, and the page is explicit about the two things it will not do. On cookies: neither. Hush will block specific scripts and elements on the website, but cannot and will not interact with the website itself and therefore will not click on any buttons, and the reason given is that under GDPR laws the user needs to explicitly consent to non-essential cookies and tracking. On ads: Hush doesn't block ads on purpose, on the stated grounds that nobody wants to read or display cookie notices, but ads, however annoying, pay for people who make things on the internet and the author does not want to steal their lunch. Two refusals, both argued rather than assumed.
The privacy claim follows from being a host, not a proxy
The privacy feature makes an absolute claim: unlike some blockers, Hush has absolutely no access to your browser habits or passwords, it does not track behavior or collect crash reports, and nothing leaves your device. The mechanism section is what makes that plausible, and it is one sentence: the app is primarily a host of rules that integrates with Safari in a native, lightweight way. So the trust story is structural. There is no server to send anything to because there is no server, and the rules execute inside Safari rather than being fetched at request time. The only size figure on the page is consistent with that, with the download under half a megabyte, which is a rule set and an app shell rather than a bundled browser engine.
Both platform links point at one App Store listing
The download section has an iOS heading and a macOS heading, and both carry the same App Store identifier.
https://apps.apple.com/app/id1544743900What differs is the stated floor: iOS 14 or later for the first, macOS 11 or later for the second. The macOS section also adds a direct download of a `.dmg` from the GitHub releases, which the iOS section has no equivalent of, so a macOS user can sideload and an iOS user cannot. The setup step is the same either way, described as being as easy as downloading the app and enabling it in Safari settings under Content Blockers, with no configuration or maintenance needed. There is no browser extension for anything else, and the page does not mention one.
Building the app needs Deno, and the rule list is generated
The build instructions put a JavaScript runtime ahead of Xcode.
brew install deno
xcode-select --installDeno then does three separate jobs in a Swift project. It formats and checks the scripts with `deno fmt` and `deno fmt --check`. It runs the unit tests with `deno test`, so the blocklist tests are Deno tests rather than XCTest. And it runs the two build scripts: `fetch_external` executes a script with write access to `./data` and network access, and `blocklist` executes another with read access to `./data` and access to a `MINIFY` environment variable. So `data/` holds both the fetched upstream material and the compiled output, and the rule list is produced during the build rather than committed as finished JSON.
A make target that refuses to run outside Xcode
One Makefile target is deliberately unusable from a shell. The `xcode` target checks two environment variables and stops with a make error if either is unset.
$(error CONFIGURATION_BUILD_DIR env is not set, make this command is run from Xcode)The same guard exists for `UNLOCALIZED_RESOURCES_FOLDER_PATH`, and the error text says the command is run from Xcode. What the target does is create the unlocalized resources directory, run the blocklist target with `MINIFY=1`, and redirect the output into `blockerList.json` inside that folder. In other words the rule list is generated as a side effect of an Xcode build, with its destination chosen by Xcode rather than by the Makefile. That is a coherent design for a resource bundle that has to land in a specific place, and it does mean the documented make interface covers only part of the build.
The UI test suite is pinned to one simulator name
There are two test targets and two runtimes. The combined `test` target runs `test_unit` and then `test_ui`.
make test_uiThe unit side is `deno test`, which as noted is Deno rather than Swift. The UI side is a single `xcodebuild test` invocation against the Hush.xcodeproj, the Hush iOS scheme, and a destination of `platform=iOS Simulator,name=iPhone 17`. Pinning a destination by device name rather than by identifier means the command depends on the simulator list installed on the machine running it, and the name will need changing each time Apple renames or retires a device. It is also a very visible reminder of how old the release is: the one tagged build predates every device name the suite now names.
The app is MIT and the rules inside it are CC BY 3.0
The licence block at the bottom of the page carries two entries and they are not the same. Hush itself is under the MIT License, copyright Joel Arvidsson 2020-present. The Fanboy List, taken from easylist.to, is under CC BY 3.0, copyright Rick Petnel and contributors 2005. So the application code is permissively licensed and the rule list it ships is a Creative Commons attribution licence with a different holder and a copyright fifteen years older than the app. Anyone rebuilding the blocklist or redistributing the app has to satisfy both, which the page states without commentary. Funding is described the same way, with everything free of charge forever and no in-app purchases, plus a footnote asking for help towards the yearly Apple Developer fee.
Editorial conclusion
Hush is the right choice if you are annoyed by consent dialogs rather than by advertising, because that is the whole scope and the app says so instead of expanding it. Two things to know first. It deliberately does not decide cookie consent for you, on the grounds that the law requires you to give it, so anything that depends on a site reading a cookie choice still needs you to click. And the licensing is split: the application code is MIT while the rule list it ships is CC BY 3.0 under a different holder, so read both before you redistribute anything derived from it.
Frequently asked questions
Is the Hush app a legitimate app?
The page carries an endorsement from John Gruber of Daring Fireball, dated 23 January 2021, recommending Hush to anyone who uses Safari. The app is free with no in-app purchases, is described as having no access to your browser habits or passwords and collecting no crash reports, and its source is published under the MIT license.
Is there a Hush extension for Safari?
There is no extension. Hush is an app that registers as a content blocker, and enabling it means turning it on in Safari settings under Content Blockers. The page says no configuration or maintenance is needed, and the app is primarily a host of rules that integrates with Safari natively.
What does the Hush app do?
It blocks the cookie consent nags and privacy-invasive tracking in Safari by blocking specific scripts and elements on the page. It does not accept or deny cookie permission itself and will not click buttons, and it does not block ads on purpose.
Is there an iPhone app called Hush?
Yes. The iOS download requires iOS 14 or later and the macOS download requires macOS 11 or later, and both point at the same App Store listing. The macOS section additionally offers a direct .dmg download from the GitHub releases, which the iOS section does not.
Official sources
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.
[](https://hysenlabs.com/projects/oblador-hush)Star history chart for your README
[](https://hysenlabs.com/projects/oblador-hush)Was this useful?