Open-source project
oliverschwendener/ueli avatar
oliverschwendener/ueli

ueli: a keystroke launcher whose release builds are deliberately unsigned

Cross-Platform Keystroke Launcher

4,617 stars273 forksTypeScriptMIT

At a glance

What is it?
Ueli is an Electron keystroke launcher for Windows, macOS and Linux with 23 bundled extensions and an Alt+Space hotkey, and the one thing every installation guide leads with is that the binaries are not signed.
Who is it for?
Adopt ueli if you want a keyboard-driven launcher with extensions you can toggle one at a time and a Windows Store install that does not need you to think about signing. Do not adopt it on a managed macOS or Wayland machine without reading the caveats, because the binaries are unnotarized and global hotkeys may not register under Wayland.
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 3 days ago.
What is it written in?
Mainly TypeScript, 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

  • oliverschwendener/ueli4,617 ★ · +13
Star history
Repository2026-09-232026-11-15
oliverschwendener/ueli4.6k4.6k

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

Editorial analysis

The binaries are unsigned, and both platforms object

The installation section opens with a sourcing instruction rather than a download link: download Ueli only from the Microsoft Store, the website at https://ueli.app, or the repository. That framing exists because of what follows.

On Windows, the README says you can manually download and install from the releases page, but notes that due to cost reasons these binaries are not signed and Windows will prevent you from installing or opening the app.

On macOS the same note is slightly longer: due to cost reasons, these binaries are neither signed nor notarized, and because of that macOS will prevent you from installing or opening the app. The workaround is spelled out as a first-launch ritual: when you try to launch it, macOS blocks it, and you open System Settings, go to Privacy & Security and click Open anyway.

So on two of the three platforms the first run is an instruction to override a security prompt. That is a decision about trust made once per machine, and it is the first thing to understand about this project.

winget install Ueli -s msstore is the supported Windows route

Given the unsigned releases, the Store is the answer on Windows. The README gives the Store listing and a winget command:

bash
winget install Ueli -s msstore

The -s msstore flag is what routes winget at Microsoft's store rather than at winget's own package index, which is the difference between a signed store install and a sideloaded one.

That is why the sourcing sentence names only three places, one of which is this repository. On Linux there is nothing to say beyond downloading from the releases page, since Linux has no equivalent notarisation gate and no Store listing in the instructions.

So the platform story is uneven by design: Windows has a proper signed channel, macOS has a documented override, and Linux has a plain download. Anyone deploying this across a fleet should notice that the three platforms do not have the same security posture.

Alt+Space opens it, Cmd+K opens the actions menu

The first steps section is the whole keyboard model, and it is short enough to use as a reference.

When you launch the app the main window appears and you can start typing for what you are looking for. Alt+Space shows and hides Ueli. The arrow keys navigate the result list and Enter launches the selected item. Additional actions on the selected result open with Cmd+K on macOS or Ctrl+K on Windows and Linux, where the arrow keys navigate, Enter invokes, and Escape closes.

Favourites come from that menu: Add to Favorites puts an item permanently at the top of the result list, and removing one is either Remove from favorites in the same menu or the x icon in Settings, under Favorites. Settings itself opens with Cmd+, or Ctrl+, on Windows and Linux, or from the Settings button.

For anyone comparing launchers, the hotkey is Alt+Space rather than the Command or Win key.

23 extensions, each toggled by one switch

Extensions are managed from the left navigation: click Extensions, toggle a switch to enable or disable an extension, and an additional item appears in that navigation holding the settings for that specific extension.

The bundled list is long enough to be the project's real feature list. Appearance Switcher, Application Search, Base64 Conversion, Browser Bookmarks, Calculator, Color Converter, Currency Conversion, Custom Web Search, DeepL Translator, File Search, JetBrains Toolbox, Password Generator, Quick Formatter, Rowland Text Editor, Simple File Search, System Commands, System Settings, Terminal Launcher, Ueli Commands, UUID / GUID Generator, Visual Studio Code, Web Search and Windows Control Panel.

Two of those names describe the scope. Application Search and System Commands sit next to Web Search, so this is a launcher that indexes what is installed and can run system commands, not only a fuzzy finder over applications.

Each extension has its own README under docs/Extensions/, and more general information lives in the project wiki. Enabling one is a single switch rather than a config file, which is what makes the list feel less like a plugin system and more like a settings page.

The Settings section of the README says under construction

There is a Settings section in the README and it contains a warning emoji and two words: Under construction.

That is the whole of it, and it is worth noticing because Settings is where the application documents everything else. It is where Debugging lives, and the debugging section says that if something does not work as expected you go to Settings and click Debug, where you might find some logs that help find the issue.

So the application's own log viewer is documented in one line and its settings are documented in none. A user configuring hotkeys, index scope or appearance is working from the interface rather than from documentation.

For an adopter this is the practical limit on evaluation. What the launcher does out of the box is documented in full, and what you can tune is not, so the only way to judge the configuration surface is to install it and open the window.

Wayland breaks the global hotkey, and the CLI is the fallback

There is a known issues section, and it has one entry, under Linux. Global hotkeys may not work under Wayland sessions.

The workaround it gives is a command line rather than a setting. Bind a custom shortcut in your system settings to call ueli to show and focus the main window, or to call ueli --toggle to toggle the main window.

Two things follow. The binary is invocable, so the launcher is scriptable in a way a menu-only launcher is not, and the Wayland session takes away the feature that makes a keystroke launcher worth having unless you wire the key yourself.

That is the only known issue listed, which is worth saying plainly as well: a project can be nearly-release quality in its README's language and still have one platform gap like this. GNOME on Wayland is the case to test before you roll it out.

oxlint, oxfmt and tsc -b, with an Electron Vite beta

The development section lists nine commands, and package.json holds the interesting detail behind them. Linting is oxlint ., formatting is oxfmt with separate check and write variants scoped to src and docs markdown, and typecheck is tsc -b.

One script chains the rest:

json
"check": "npm run typecheck && npm run lint && npm run format:check && npm run test",

So typecheck, lint, format check and tests are a single gate, which is the shape you want in CI.

The dependencies explain the rest. electron at version 45 with electron-builder at 26 package the app, electron-vite is at 6.0.0-beta.1, a beta in the build tool, and vitest, typescript at 7 and vite at 8 do the rest. Types for better-sqlite3 are in the dev dependencies, so a SQLite binding is in play, and @fluentui/react-components is the first runtime dependency, which is where the Windows-flavoured look comes from.

Build and package are separate steps, electron-vite build and then electron-builder --config electron-builder.config.js, and a postinstall hook runs electron-builder install-app-deps to rebuild native modules.

Node.js 24 and commit signing to contribute

The requirements for contributing are three lines, and two of them are unusual. Node.js 24. Make sure you have commit signing enabled. And, optionally, if you use Visual Studio Code, install the recommended extensions.

Commit signing as a requirement rather than a suggestion is the kind of policy a maintainer sets once and keeps. Node 24 as a floor is the other, and it matches the toolchain in the manifest, where typescript, vite and vitest are all current majors.

The rest of the workflow is the usual npm sequence. npm install to set up, npm run dev for the app in development mode, then the quality checks as separate commands: format:check, format:write, lint, typecheck and test. Build and package are npm run build and npm run package.

The root of the repository holds five tsconfig files, tsconfig.json plus base, common, node and web, which is the usual shape for an Electron app where the main process and the renderer are checked separately, plus oxlintrc.json, oxfmt.config.mts, electron.vite.config.mts and vitest.config.mts.

Editorial conclusion

Adopt ueli if you want a keyboard-driven launcher with extensions you can toggle one at a time and a Windows Store install that does not need you to think about signing. Do not adopt it on a managed macOS or Wayland machine without reading the caveats, because the binaries are unnotarized and global hotkeys may not register under Wayland. Two things to check before you rely on it: whether your platform blocks unsigned software, which is the first-launch hurdle on two of the three, and whether the extension you want exists, since Settings itself is documented as under construction.

Frequently asked questions

How do I install Ueli on Windows?

From the Microsoft Store, either through the Store listing or with winget install Ueli -s msstore. Binaries from the GitHub releases are not signed, so the README says Windows will prevent you from installing or opening them.

Why does macOS refuse to open Ueli?

Because the release binaries are neither signed nor notarized, for cost reasons as the README puts it. macOS blocks the app on first launch, and the documented workaround is to open System Settings, go to Privacy & Security and click Open anyway.

How do I add an item to Ueli's favorites?

Open the additional actions menu for a search result with Cmd+K on macOS or Ctrl+K on Windows and Linux, then choose Add to Favorites, and the item appears first in the list from then on. Removing one is either Remove from favorites in that menu or the x icon under Settings, then Favorites.

Does Ueli work under Wayland on Linux?

Global hotkeys may not work under Wayland sessions, which is the project's one listed known issue. The workaround is to bind a system shortcut to run ueli to show and focus the main window, or ueli --toggle to toggle it.

What extensions does Ueli ship with?

Twenty three, each with its own README under docs/Extensions/. They include Application Search, Web Search, Calculator, Color Converter, Currency Conversion, DeepL Translator, Password Generator, Terminal Launcher, System Commands, Visual Studio Code, JetBrains Toolbox and Windows Control Panel.

Official sources

  1. License: MIT
  2. oliverschwendener/ueli 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/oliverschwendener-ueli.svg)](https://hysenlabs.com/projects/oliverschwendener-ueli)

Star history chart for your README

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

Was this useful?