Automic VaultAutomic Vault

brew

Install zapp with Homebrew

Flash ZSA keyboards from your terminal. Version 1.0.2 via Homebrew; verified 2026-07-09.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrewverified ยท 100%
brew install zapp

local Homebrew formula metadata

overview

Package summary

Flash ZSA keyboards from your terminal

Commands and aliases

  • zapp

history

Project history and usage

Zapp is ZSA Technology Labs' open-source Rust CLI for flashing ZSA ergonomic keyboards from a terminal instead of using a browser or the larger Keymapp application.

Project history

ZSA introduced Zapp on 2026-04-07 as a small terminal tool for users who do not flash through a browser and want something lighter or more automation-friendly than Keymapp. The README describes it as a cross-platform CLI for flashing ZSA keyboards including Voyager, Moonlander, Ergodox EZ, Halfmoon, and Planck EZ variants.

The project structure is intentionally split between a `zapp` CLI binary and `zapp-core` library code for USB device detection, firmware parsing, and flashing protocols such as STM32 DFU and HALFKAY.

Adoption history

Zapp's adoption is young and vendor-specific. Its README already documents Homebrew, openSUSE, Arch/AUR, Nix flakes, source installation through Cargo, release binaries, and Linux udev rules, which is the right packaging surface for a USB firmware-flashing tool.

The ZSA announcement positions Zapp as automation-friendly: it can flash a local firmware file or Oryx URL, and `zapp update` can read layout and revision data from a keyboard flashed with Oryx firmware without storing login credentials.

How it is used

Users run `zapp flash firmware.bin`, `zapp flash firmware.hex`, or pass an Oryx layout URL. Zapp downloads or parses the firmware, waits for the keyboard to enter bootloader mode, detects the device over USB, and flashes it. On Linux, users need udev rules so the USB device is accessible without root.

Why package nerds care

Zapp is package-nerd significant because it turns a vendor hardware workflow into a normal CLI package: installable with Homebrew or distro tools, auditable as open-source Rust, and friendly to repeatable firmware workflows.

It also shows the packaging details that make hardware CLIs different from pure text tools: firmware formats, USB permissions, udev rules, bootloader modes, and platform-specific flashing protocols are part of the package experience.

Timeline

  • 2026-04-07: ZSA published the Introducing Zapp announcement.
  • 2026: README documents Homebrew, openSUSE, Arch/AUR, Nix, Cargo, and release-binary installation paths.
  • 2026: Zapp supports local DFU/Intel HEX firmware files, Oryx URLs, and keyboard-layout update checks.

Related projects

  • Related projects include ZSA Oryx, ZSA Keymapp, Wally, QMK Firmware, QMK Toolbox, kontroll, dfu-util-style firmware workflows, and keyboard-specific udev rule packages.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for zapp. Nucleus package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
zappcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-25
manager version1.0.2
manager updated2026-07-09
local dataok
upstreamcurrent
latest detectedv1.0.2

https://github.com/zsa/zapp

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:zapp
Version1.0.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/zapp
Homepagehttps://github.com/zsa/zapp
Repositoryhttps://github.com/zsa/zapp
Upstream docshttps://github.com/zsa/zapp#readme
LicenseMIT
Source archivehttps://github.com/zsa/zapp/archive/refs/tags/v1.0.2.tar.gz
Last updated2026-07-09T11:51:39Z
Pulseupdated
Build dependenciesrust
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namezapp
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

Related tools

  • rustBuild dependency declared by Homebrew.

Same workflow

  • create-dmgShares av.db curated category or tags: cli, developer-tools, macos, packaging.
  • objc-runShares av.db curated category or tags: cli, developer-tools, macos.
  • abi3auditShares av.db curated category or tags: cli, developer-tools, packaging.
  • auditwheelShares av.db curated category or tags: cli, developer-tools, packaging.
  • brew-gemShares av.db curated category or tags: cli, developer-tools, packaging.
  • brew-php-switcherShares av.db curated category or tags: cli, developer-tools, macos.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment