Automic VaultAutomic Vault

brew

Install lzsa with Homebrew, Nix

Lossless packer that is optimized for fast decompression on 8-bit micros. Version 1.4.1 via Homebrew; verified from local package data.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install lzsa

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#lzsa

nixpkgs package indexes · pkgs/by-name/lz/lzsa/package.nix · source: api.github.com

overview

Package summary

Lossless packer that is optimized for fast decompression on 8-bit micros

Commands and aliases

  • lzsa

history

Project history and usage

LZSA is Emmanuel Marty's byte-aligned lossless packer family optimized for very fast decompression on 8-bit computers. Its upstream README describes LZSA1 and LZSA2 as formats designed to beat familiar retrocomputing tradeoffs: LZSA1 as an LZ4-like choice for 8-bit scenarios, and LZSA2 as a ZX7-like choice with much faster decompression.

Project history

LZSA is not a general Unix compressor in the gzip tradition. It is a modern tool built for old hardware constraints: small decompressors, simple byte-aligned decoding, limited 8-bit arithmetic, and assets that must unpack quickly on Z80, 6502, 8088, 6809, 6309, and related targets.

The repository combines a command-line compressor, formal stream/block format documents, benchmark comparisons, and contributed assembly depackers. Releases through the 1.3 and 1.4 series focused on ratio improvements, faster LZSA2 compression, and a growing collection of platform-specific depackers.

Adoption history

LZSA's adoption is concentrated in retrocomputing, demoscene, and homebrew game development rather than mainstream system archives. The official README lists concrete uses including ZX Spectrum demos, Apple II projects, Commander X16 ROM work, RomWBW, rasm-compressed data sections, and Amstrad CPC game assets.

Package-manager adoption is correspondingly smaller than LZ4 or lzip. The input package facts show Homebrew and Nix packages, enough to make the compressor easy to install on developer machines even though the decompression targets are often vintage CPUs.

How it is used

Developers run the lzsa tool on modern systems to pack assets, then include the matching depacker on the target machine. The key choice is not just compression ratio but the decompressor's speed and code size on a specific CPU.

The upstream format documentation supports implementers who need to write or audit their own depackers, which is common in size-constrained retro projects.

Why package nerds care

LZSA is package-nerd significant because it is a niche tool with real cross-compilation value: the package runs on modern macOS/Linux build hosts but exists to feed 8-bit runtime environments.

It also shows a different kind of compression packaging pressure. For LZSA, the artifact that matters may be a 67-byte Z80 depacker or a 6502 speed-optimized routine, not a shared library ABI.

Timeline

  • 2010s: LZSA appears as a retrocomputing-focused compressor and format family.
  • 2019-2020: Upstream README records use in demos, games, and ROM projects across Z80, 6502, and related systems.
  • 2023: GitHub releases include the 1.4.x series, continuing performance and depacker work.

Related projects

  • LZ4 is an explicit design reference for LZSA1.
  • ZX7 is an explicit comparison point for LZSA2.
  • Lizard/LZ5 and other optimal packers appear in upstream comparisons.

security posture

Risk level: blue

broad file, network, media, or database tool signal.

Risk classifier

blue risk · medium confidence · tool

Why

  • broad file, network, media, or database tool signal

Signals

  • text:compress

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 8 platform targets.

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
lzsacliglobal 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-08
manager version1.4.1
manager updated
local dataok
upstreamcurrent
latest detected1.4.1

https://github.com/emmanuel-marty/lzsa

  • infoNo package-manager update timestamp was available.low confidence

install metadata

Package metadata

Package keybrew:lzsa
Version1.4.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/lzsa
Homepagehttps://github.com/emmanuel-marty/lzsa
Repositoryhttps://github.com/emmanuel-marty/lzsa
Upstream docshttps://github.com/emmanuel-marty/lzsa#readme
LicenseZlib AND CC0-1.0
Source archivehttps://github.com/emmanuel-marty/lzsa/archive/refs/tags/1.4.1.tar.gz
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

lzsa

nix profile install nixpkgs#lzsa
  • normalized package name match
  • Matched by: Lzsa
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/lz/lzsa/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

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
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment