Installation
Install Loupe on macOS, Linux or Windows, and verify what you downloaded.
Loupe ships as a native binary for macOS, Linux and Windows. The current release is v0.1.7 — see the release notes for what changed. Every build is on the latest release page.
The cask resolves the correct architecture:
brew install --cask kryptonhq/tap/loupeAlternatively, download a .dmg from the
latest release —
aarch64 for Apple Silicon, x64 for Intel. The architectures are
built separately rather than as a universal binary, so each download
contains one slice.
Signed and notarised since v0.1.2
The macOS builds are signed with a Developer ID and notarised, with the ticket stapled, so the app opens on a double-click. There is nothing to allow in System Settings and no quarantine attribute to remove.
Loupe also updates itself from v0.1.5 onward, so brew upgrade is only
needed to reach that version. The cask is marked auto_updates true;
pass --greedy if you would rather Homebrew drive the upgrade.
Verifying a download
macOS builds are verified by Gatekeeper on open. Linux builds carry a
detached GPG signature per file — Loupe_<version>_amd64.deb.asc beside
Loupe_<version>_amd64.deb, and likewise for the .rpm and
.AppImage.
Import the release key, published in the repository at
packaging/linux/loupe-release.asc,
and check that its fingerprint is
CC01 D01D 4A8B 455D CC67 EED5 1D2D 0C2A 56D7 8DD0 — the same value is in
packaging/linux/README.md —
before trusting it:
curl -fsSLO https://raw.githubusercontent.com/kryptonhq/loupe/main/packaging/linux/loupe-release.asc
gpg --import loupe-release.asc
gpg --fingerprint "Loupe Release Signing"Then verify whichever format you downloaded:
| Format | Verify |
|---|---|
.deb | gpg --verify Loupe_<version>_amd64.deb.asc Loupe_<version>_amd64.deb |
.rpm | gpg --verify Loupe-<version>-1.x86_64.rpm.asc Loupe-<version>-1.x86_64.rpm |
.AppImage | gpg --verify Loupe_<version>_amd64.AppImage.asc Loupe_<version>_amd64.AppImage |
Look for Good signature from "Loupe Release Signing". The warning that
the key is not certified with a trusted signature is expected unless you
have signed the key yourself.
The .sig files in each release are minisign signatures used by the
built-in updater, not GPG signatures, and do not verify with gpg.
Releases published before Linux signing was introduced have no .asc
files.