Automic VaultAutomic Vault

brew

lzsa mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für lzsa in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install lzsa

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#lzsa

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

Überblick

Paketzusammenfassung

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

Befehle und Aliase

  • lzsa

Verlauf

Projektgeschichte und Nutzung

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.

Projektgeschichte

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.

Adoptionsgeschichte

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.

Wie es verwendet wird

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.

Warum Paket-Nerds sich dafür interessieren

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.

Zeitleiste

  • 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.

Sicherheitslage

Risikostufe: blue

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

Risikoklassifikator

blue Risiko · mittel Konfidenz · tool

Warum

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

Signale

  • text:compress

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 8 Plattformziele verfügbar.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
lzsacliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version1.4.1
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Version1.4.1

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

  • InfoNo package-manager update timestamp was available.niedrig Konfidenz

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:lzsa
Version1.4.1
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/lzsa
Homepagehttps://github.com/emmanuel-marty/lzsa
Repositoryhttps://github.com/emmanuel-marty/lzsa
Upstream-Dokumentationhttps://github.com/emmanuel-marty/lzsa#readme
LizenzZlib AND CC0-1.0
Quellarchivhttps://github.com/emmanuel-marty/lzsa/archive/refs/tags/1.4.1.tar.gz
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

lzsa

nix profile install nixpkgs#lzsa
  • normalized package name match
  • Abgeglichen nach: 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

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • 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