Vorssaint: one menu bar icon, and what stops working when you install less of it
Free and open-source macOS menu bar toolkit. Super key. Hold Caps Lock and it counts as Shift, Control, Option and Command together, so the shortcuts you build on it never fight with the ones apps already use.
At a glance
- What is it?
- Vorssaint is a Swift menu bar toolkit for macOS that bundles a system monitor, per-app audio mixer, app switcher, window snapping, clipboard history and an uninstaller behind a single icon, where the interesting design decisions are the per-feature install, the permission that each one asks for and the beta-labelled Fan Control.
- Who is it for?
- Use Vorssaint if you want a broad set of Mac utilities in one process and you are willing to pick features one at a time, because that choice is what keeps its permission footprint small (setup asks only for the permissions your choices need). Be careful with the Super key, with features whose support is stated as a list of compatible apps and supported devices, and with Fan Control, which is labelled beta.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- 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 13, 2026, and from our analysis. They are not legal advice.
Star history
- vorssaint/vorssaint-utils34,606 ★ · +30,810
| Repository | 2026-08-02 | 2026-11-13 |
|---|---|---|
| vorssaint/vorssaint-utils | 3.8k | 34.6k |
30,810 Stars in the last 103 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Uninstalled features stop loading, so the permission ask shrinks with your choices
The install model is per feature rather than all or nothing. You choose individual features or start from a preset, and anything you do not pick stops loading and disappears from the interface. Reinstalling a feature restores the settings it had before, so the cost of an experiment is reversible rather than permanent. Setup asks only for the permissions your selections need, which is the point of the exercise: a panel with a dozen toggles on and a panel with three on do not carry the same system access. The consequence for a reader is about time rather than privacy alone. A permission granted at first launch does not cover a feature you enable three weeks later, so adding a feature later may mean a new permission prompt.
The app switcher has a mode that gives up live previews on purpose
The app switcher switches between apps and windows with live previews, search and display filters, and it ships a simpler mode that works without screen capture. That second mode is the design decision worth reading twice, because previews are the part that needs the most invasive permission and the part users are most often unwilling to grant. Without it you still get app and window switching, and you lose the picture. Dock Preview follows the same shape, hovering a Dock icon to preview windows across desktops and then switching, closing, moving or snapping them from the preview. The consequence is that what the app switcher can do is partly a function of a privacy decision you make once, and granting screen recording to get thumbnails is a larger concession than granting it to read a window title. The Dynamic Island panel follows the same hardware dependency, describing controls kept around the camera cutout, so a Mac without one gets little from it.
Support is written as lists of devices and apps, not as a capability check
Several features describe their reach with the same vocabulary. Microphone tools adjust the input level on supported devices. Side buttons work in Finder, browsers and compatible apps. Keyboard shortcut takeover applies to supported macOS shortcuts and only while a feature is active. Mouse enhancements can be limited to a set of apps to leave alone, and the Super key carries its own app exclusions. The pattern is consistent and it has one consistent failure mode: on hardware or software outside the named set, the toggle can be on and the effect can be absent. For someone assembling a shortcut sheet, that means you verify each combination on the apps you actually use, rather than trusting the toggle state. The exclusion lists are also the escape hatch, which means the same feature is both your best tool and your first suspect when it misfires.
Super key makes Caps Lock read as four modifiers at once
This is the mechanism the project leads with. Hold Caps Lock and it counts as Shift, Control, Option and Command together, so a shortcut you build on it does not collide with combinations applications already claim. You can use Caps Lock or a right-side modifier, give the key its own separate tap action, and exclude specific apps. The design point is that a four-modifier chord is free in most apps, so it becomes a namespace of its own. The consequence is the mirror image of the benefit: inside any app you have not excluded, the key is no longer Caps Lock, it is four modifiers pressed at once. Apps that read modifiers for their own gestures, text entry tools that depend on Caps Lock, and anything listening for a key that is down for a while all see something different from what a stock keyboard sends. The exclusion list is therefore not a convenience setting, it is the part of the feature you have to curate.
Fan Control remains labelled beta
The release trail is dense. v3.4.2-beta.2 went out on 2026-10-20, v3.4.2 on 2026-10-21 and v3.4.3 on 2026-10-29, with the repository last pushed on 2026-10-30. The newest tag, v3.4.3, is a stable release, and the project ships continuously rather than in quarterly batches. Inside the feature list, Fan Control is the item that carries a beta label, covering manual fan speeds, temperature curves and live RPM. So even on the newest stable tag, fan control is still labelled beta as a feature.
Auto clear empties the system clipboard but keeps the app's own history
Clipboard history stores local text, image and file entries that you can search, pin, preview and paste with shortcuts. Auto clear wipes the system clipboard after a delay, after sleep or after lock, and the description says it does that while keeping saved history. So the two halves are deliberately separated, which is useful if you want the system clipboard to stop holding a password you copied and useless as a privacy control if the sensitive thing also got captured into the local history. Paste as plain text behaves the same way, restoring formatting only at the paste and preserving the original clipboard content rather than replacing it. Adjacent tools follow the same pattern of reversible or non-destructive action: pointer acceleration restores your previous setting when the feature is turned off, and Clean URL strips tracking parameters from links manually or automatically.
SwiftPM and build.sh sit in the repo, but the page ships a downloaded app
The repository is laid out as a Swift package: Package.swift, Sources/, Tests/, Tools/, Resources/, ReleaseAssets/ and a build.sh, alongside CHANGELOG.md, CONTRIBUTING.md, SUPPORT.md, SECURITY.md, a separate TRADEMARKS.md and a GPL-3.0 LICENSE. The page links an Install section, a What you need section, the GitHub releases page and the site at vorssaint.com, and the repository has a GPL-3.0 licence with the mark handled separately in TRADEMARKS.md. Support runs through [email protected] and a Discord invite, with a donation link at buymeacoffee, and settings can be exported to another Mac. Check the What you need section for the macOS version and hardware requirements.
Editorial conclusion
Use Vorssaint if you want a broad set of Mac utilities in one process and you are willing to pick features one at a time, because that choice is what keeps its permission footprint small (setup asks only for the permissions your choices need). Be careful with the Super key, with features whose support is stated as a list of compatible apps and supported devices, and with Fan Control, which is labelled beta. Before installing, read the Install and What you need sections on the project page, check whether the macOS version and the hardware you rely on are covered, and decide in advance whether you will take a stable tag or a beta, since recent releases (v3.4.2-beta.2, v3.4.2, v3.4.3) landed within about nine days.
Frequently asked questions
What is vorssaint?
Vorssaint is a free and open-source macOS menu bar toolkit written in Swift. It puts a system monitor, an app switcher, window snapping, Dock previews, clipboard history, text snippets, a file shelf and an uninstaller behind a single menu bar icon, with no account, no telemetry and no subscription.
What is the best utility software for Mac?
Vorssaint's own claim is one menu bar icon doing the job of a dozen paid Mac apps. What separates it from a plain launcher bundle is per-app volume mixing with no audio driver required, per-feature installation so unused features do not load, and the Super key, where holding Caps Lock counts as Shift, Control, Option and Command together so your shortcuts do not fight the ones apps already use.
How do I get to Mac utilities?
The project page links an Install section and a What you need section, and points to the GitHub releases page and the website at vorssaint.com for the download.
What is the utilities app on a Mac?
Vorssaint describes itself as a menu bar toolkit, not a system utility: a single menu bar icon adds a system monitor, an app switcher, window snapping, Dock previews, clipboard history, text snippets, a file shelf and an uninstaller. You install the features you want, reorder or hide panel sections, choose a compact layout, and export settings to another Mac, in more than a dozen languages.
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/vorssaint-vorssaint-utils)[](https://hysenlabs.com/projects/vorssaint-vorssaint-utils)Star history chart for your README
[](https://hysenlabs.com/projects/vorssaint-vorssaint-utils)Was this useful?