# Cork: a SwiftUI front end for Homebrew, and what it adds beyond brew

> Cork is a macOS GUI for Homebrew written in SwiftUI, distributed as a paid pre-compiled app or built from source. It claims faster package listing and features brew does not expose, but its build instructions are strict and the licence file is not a standard SPDX identifier.

**buresdv/Cork** — [NO AI] Fast GUI for Homebrew written in SwiftUI

- Repository: https://github.com/buresdv/Cork
- Website: https://corkmac.app
- Stars: 4,704 · Forks: 277
- Language: Swift
- License: NOASSERTION
- Published: 2026-09-23 · Updated: 2026-09-23 · Language: en
- Canonical page: https://hysenlabs.com/projects/buresdv-cork

## What Cork is for, and who it is aimed at

Cork is a macOS application that puts a graphical interface over Homebrew. The README describes it as "a fast GUI for Homebrew written in SwiftUI", and the repository topics list homebrew, homebrew-cask, macos-app and swiftui. The audience is Mac users who already run Homebrew and find the command line awkward for routine maintenance: seeing what is installed, what is outdated, what depends on what.

The README is explicit that Cork is not only a wrapper. It lists features it says are not possible without Cork, including automatically respecting the system proxy, clearing cached downloads, updating packages from the menu bar while Cork is closed, and tagging packages. A second list covers tasks Cork makes easier: listing installed packages, distinguishing intentional installs from dependencies, updating selected packages, and showing which packages a given package is a dependency of. That second list is the more interesting one, because it names `brew leaves` as the closest command line equivalent and calls it "often unreliable".

So the target user is not someone who has never touched a terminal. It is someone who uses Homebrew regularly, has a long package list, and wants the dependency graph and update flow visible without parsing command output.

## How Cork loads your package list faster than brew

The README states that Cork "has its own way of loading packages, which is around 10 times faster than the Homebrew implementation". No benchmark, hardware or methodology is given, so treat the multiplier as the author's claim rather than a measured result. What the repository does show is the shape of the mechanism: the top level contains a Cork/ directory, a Modules/ directory and a Tests/ directory, and the README links to a file at Cork/Logic/JSON/Parse JSON.swift. That path indicates that Cork parses Homebrew's JSON output directly rather than shelling out to `brew` and rendering its human-readable text.

The dependency distinction follows from the same data. Homebrew records why a package was installed, and Cork reads that to separate packages you asked for from packages pulled in as dependencies. The README frames `brew leaves` as the command line alternative and says it is "often unreliable, often not listing packages that should be included". That is a fair criticism of a heuristic command, and it is also the clearest statement of Cork's value: it is reading structured data where the CLI offers a filtered list.

The rest of the architecture is standard for a modern Mac app. Tuist generates the Xcode project, Mise pins the Tuist version so different machines do not disagree, and the presence of .swiftlint.yml and .swiftformat at the top level means style is enforced in the repository rather than left to reviewers. The README notes one deliberate deviation from Swift convention: brackets go on their own lines.

## Getting Cork: the tap, the price, and the self-compiled route

There is no free pre-compiled download. The README says pre-compiled, always up-to-date versions come from the author's Homebrew tap, and you reach that tap in one of three ways: buy Cork for 25€ through corkmac.app, become a contributor (for example by translating the app or implementing an issue tagged `Help Wanted`), or compile it yourself.

The README credits Dmitri Bouniol and Ben Carlsson with "a way for self-compiled builds to bypass the license check", which is why a self-compiled copy works without a purchase. If you take that route, the prerequisites are macOS Ventura or newer, Xcode 16 or newer, Git and Homebrew. The README carries a warning in bold: follow the steps exactly and do not deviate unless you are a developer, including changing Xcode settings or accepting recommended Xcode "fixes", or the app might not work.

Before building, you need a developer certificate. The README says a free Apple Developer account is enough. In Xcode, open Settings, then Accounts, add your Apple ID, select it, click Manage Certificates, press the + icon and choose Apple Development, then Done.

The README also instructs you to point the terminal at Xcode, because Mise and Tuist need it:

```bash
sudo xcode-select -s /Applications/Xcode.app
```

After that, the README moves on to installing Mise and Tuist. It explains why Mise is involved: Cork uses it "to prevent conflicts arising from mismatched Tuist versions across Macs". The README text available here is truncated at that point, so the exact Mise and Tuist install commands and the final build command are not reproduced. Get them from the Compiling Cork section of the README on the repository before you start, and expect the process to take longer than installing an app.

## Where Cork gets in the way

The build path is the first limitation, and it is self-imposed by the project. Requiring macOS Ventura or newer and Xcode 16 or newer excludes older Macs and anyone who does not want a full Xcode install. The README's warning against accepting Xcode's recommended fixes is unusual and worth taking literally: it means the generated project is sensitive to settings Xcode would normally adjust, and a well-meaning click can produce an app that does not work. There is no documented rollback if a build goes wrong, and the README does not describe how to uninstall a self-compiled build.

The licence is the second thing to check. The repository metadata reports the licence as NOASSERTION, and the top level has a LICENSE.md. That means the licence could not be matched to a standard identifier automatically. Read LICENSE.md yourself before you redistribute anything; nothing in the README or the repository listing states terms in plain terms.

Third, Cork is macOS only, and that is a design decision rather than a gap. Homebrew runs on Linux too, and Cork will not follow you there. If your package management spans both, Cork covers half of it.

Finally, the paid model cuts against the open source habit of downloading a binary and moving on. 25€ buys all future versions at no additional cost, per the README, but the pre-compiled app is not free, and the free route costs an afternoon and a developer certificate.

## Cork against Cakebrew, Applite and WailBrew

The alternatives people search for alongside Cork are Cakebrew, Applite and WailBrew, and they differ mainly in what layer of Homebrew they present. Cork aims at the full formula and cask model: dependencies, taps, services and maintenance, with a package detail view that the README says shows "this much info about a package in one convenient location".

Applite takes the opposite position. It is aimed at casks, the GUI applications Homebrew can install, and presents them as a browsable app catalogue. If your use of Homebrew is mostly installing and updating Mac apps, that framing is closer to the task than Cork's package-and-dependency model, and the surface area is smaller.

Cakebrew is the older graphical client and follows the plain list-and-buttons approach: installed formulae, outdated formulae, search, install. It does not claim the dependency distinction, the tagging system or the menu bar updater that Cork's README describes. WailBrew is a lighter web-technology client in the same spirit as Cakebrew.

The honest summary is that Cork is the most ambitious of the four and the only one in this group that charges for a pre-compiled build. If you want a free binary and a small feature set, one of the others fits. If you want the dependency graph, tags and services in one window, that is Cork's territory.

## Maintenance, updates and what the project asks of you

The repository is not archived, and the last push was on 2026-09-20, three days before this writing. Releases have been frequent: v2.0.0 on 2026-08-24, v2.0.1 on 2026-09-11, and v2.0.2 ("Golden Gate") on 2026-09-14. That cadence matters because Cork tracks Homebrew, and Homebrew changes. A GUI that parses Homebrew's JSON has to keep up with that output format.

Upgrade cost depends on how you got the app. If you bought it, the README says you get all future versions at no additional cost, and the tap is described as always up to date. If you compiled it, every update means repeating the build, with the same Mise-pinned Tuist version and the same Xcode caveats. That is the real price of the free route: not one afternoon, but one afternoon per upgrade you care about.

Contributing has its own entry cost. The README asks contributors to respect the coding style and points at a specific deviation from Swift convention, with brackets on their own lines, linking to Parse JSON.swift as the example. Translation is handled through Crowdin, to judge by crowdin.yml at the top level, and the README recommends joining the Discord to hear when new text is ready. The AI policy is stated at the top: "Absolutely no AI is used to create any part of the app. All code and documentation is completely human-made." If you plan to contribute generated code, that policy is the first thing to read.

## Conclusion

Cork suits Mac users who manage many Homebrew packages and want tagging, dependency visibility and menu bar updates in one window, and who accept either a 25€ purchase or a source build on macOS Ventura or newer with Xcode 16 or newer. It is the wrong tool for anyone who wants a free pre-compiled download, for Linux or Windows users, and for anyone unwilling to follow the build steps exactly, since the README warns that changing Xcode settings or accepting recommended fixes can break the app. Before adopting it, verify the licence terms in LICENSE.md, confirm the current release on the tap, and check that your Mac meets the Ventura and Xcode 16 floors.

## FAQ

### Is there a Homebrew GUI for Mac?

Yes. Cork is one, described in its README as a fast GUI for Homebrew written in SwiftUI, and it runs on macOS Ventura or newer. The README also names Cakebrew-style alternatives indirectly through the ecosystem, but Cork itself is the subject here.

### Which Homebrew GUI is the best for Mac?

The repository does not rank GUIs, so no honest answer is available. Cork's README argues for Cork on specific grounds: tagging, dependency visibility, menu bar updates and proxy handling. Whether that makes it best depends on whether you need those.

### Is Homebrew still a thing?

Cork depends on it. The README lists Homebrew as a prerequisite for compiling Cork, and Cork's whole purpose is to present Homebrew's formulae, casks, taps and services in a graphical window.

### What are the current versions of Homebrew?

Cork does not track Homebrew's version numbers. Its own releases are listed as v2.0.0 on 2026-08-24, v2.0.1 on 2026-09-11 and v2.0.2 ("Golden Gate") on 2026-09-14.

## Sources

- [buresdv/Cork on GitHub](https://github.com/buresdv/Cork)
- [Issues](https://github.com/buresdv/Cork/issues)
- [Project website](https://corkmac.app)
- [README](https://github.com/buresdv/Cork/blob/main/README.md)
- [Releases](https://github.com/buresdv/Cork/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/buresdv-cork