Skip to content

Install

Builds live on tinspec.dev/download — that page carries the current files, sizes, and SHA-256 checksums, so this page does not repeat them.

There is no sign-up and no licence key. The app is fully usable the moment it opens.

A signed and notarized universal .dmg — one file for both Apple Silicon and Intel. Open it and drag Tinspec to Applications; Gatekeeper will not complain.

v0.1.0-preview.10 shipped one file: the macOS .dmg. preview.9’s Linux .AppImage, Debian .deb and Windows .exe have no preview.10 counterpart. Each release publishes the platforms it was built for, and this one was built for macOS; whether the next carries Linux and Windows is not something this page can promise you. tinspec.dev/download is the live answer.

Two consequences, both worth stating plainly:

  • An existing install keeps working and is not disturbed. The update manifest for this release names only the two macOS targets, so a Linux or Windows app is never offered preview.10. Nothing prompts, nothing half-upgrades, and the preview.9 you have keeps running.
  • There is no current Linux or Windows download. tinspec.dev/releases/ publishes the files named in the current release manifest, and preview.10’s names only the .dmg. So the download page offers macOS alone right now — not as an oversight, but because advertising a platform whose file is not published is the thing these docs are meant not to do.

The AUR package tinspec-bin repacks the released .deb. There is no preview.10 .deb, so the package was not updated for this release, and its source URL points into the same tinspec.dev/releases/ that now serves only the current release’s files. So yay -S tinspec-bin has nothing current to fetch; an already-installed copy is unaffected.

The app checks for updates on startup and shows a toast when one is available.

InstallUpdate path
macOS .dmgUpdates itself
Linux .AppImageUpdates itself — but is not offered preview.10
Linux .deb, Arch tinspec-binNotified only — update with your package manager
Windows .exeUpdates itself — but is not offered preview.10

Installs that cannot self-update say so in the toast and in About, rather than offering a button that would not work.

tinspec is a separate download on its own version line — v0.1.1, released 2026-09-13. It runs your saved chains and requests headlessly so a pipeline can fail on them. It is built against the same engine release the desktop app pins, so the two send identically.

It is macOS-only: there is no Linux and no Windows binary, and the Homebrew formula has no Linux branch.

Two commands, not one — brew tap user/repo resolves to GitHub, and this tap is on GitLab, so the URL has to be given the first time:

Terminal window
brew tap tinspec/tap https://gitlab.com/tinspec/homebrew-tap.git
brew install tinspec/tap/tinspec

Homebrew 6 may answer Error: Cannot tap tinspec/tap: invalid syntax in tap!. Nothing is wrong with the formula — that is a trust gate on a tap Homebrew does not know yet. Run the per-formula trust command and repeat the two commands above:

Terminal window
brew trust --formula tinspec/tap/tinspec

Older Homebrew has no brew trust and needs none.

For a CI image with no Homebrew, take the .tar.gz from tinspec.dev/download (the checksum is on that page) and:

Terminal window
tar -xzf tinspec_*.tar.gz && sudo mv tinspec /usr/local/bin/

The installed command is tinspec, not tinspec-cli.

The macOS build is a universal binary, Developer ID–signed and notarized. A notarization ticket cannot be attached to a bare executable, so a tarball downloaded in a browser is checked with Apple online the first time it runs; brew install and curl downloads are not quarantined and skip that.

What the commands do, what each exit code means, and what it deliberately cannot do yet are in Run a suite in CI.

First run — creating a project and finding your way around.