Automic VaultAutomic Vault

brew

authz0 mit Homebrew, Nix installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install authz0

local Homebrew formula metadata

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#authz0

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

Überblick

Paketzusammenfassung

Automated authorization test tool

Befehle und Aliase

  • authz0

Verlauf

Projektgeschichte und Nutzung

Authz0 is a Go CLI for automated authorization and access-control testing. It models target URLs, roles, assertions, and credentials in YAML templates, then scans for unauthorized access based on those role definitions.

Projektgeschichte

The public repository was created in January 2022. The README describes the tool as an automated authorization test tool that identifies unauthorized access using URLs, roles, and credentials.

Early releases moved quickly: v1.0.0 shipped in January 2022, v1.1.0 added `setCred` plus imports from ZAP, HAR, and Burp history, and v1.1.2 followed in March 2022. The repository has continued to receive activity even though Homebrew currently tracks the older 1.1.2 release.

Adoptionsgeschichte

Authz0 is distributed through Go install, Homebrew via the project's tap instructions, Snapcraft, Docker, and a GitHub Action according to official docs and the README. The Homebrew core formula packages 1.1.2 from the official GitHub tag, while the input also records Nix packaging.

The tool sits in the bug-bounty and application-security packaging lane: small enough to install as a single CLI, but designed to consume artifacts from Burp, ZAP, HAR exports, and YAML templates created during manual security testing.

Wie es verwendet wird

A typical flow is `authz0 new` to generate a YAML template, `authz0 setUrl`, `setRole`, and `setCred` to add test data, then `authz0 scan` to execute checks. The docs show credential headers stored inside the user-supplied template file rather than a fixed global credentials location.

Because the template path is chosen by the user, there is no official fixed config-file or credentials-file location to record. The official structure docs document the YAML schema, not an application config path.

Warum Paket-Nerds sich dafür interessieren

Authz0 is notable for packaging a common appsec workflow as a reproducible CLI: collect URLs from ZAP/Burp/HAR, map roles to allowed and denied routes, and run the same authorization checks again in CI or local testing.

Its package history also shows the difference between upstream activity and packaged stable versions: the repository is active, while the Homebrew stable formula remains at the 2022 1.1.2 release.

Zeitleiste

  • 2022-01: Public GitHub repository created.
  • 2022-01: v1.0.0 released.
  • 2022-01: v1.1.0 added `setCred` and ZAP/HAR/Burp import flags.
  • 2022-03: v1.1.2 released.
  • 2022-05: GitHub Action release tag published.

Related projects

  • Authz0 is designed to work around artifacts from OWASP ZAP, Burp Suite, HAR files, Docker, GitHub Actions, and Go-based CLI installation.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

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
authz0cliglobales 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-25
Manager-Version1.1.2
Manager aktualisiert
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.1.2

https://github.com/hahwul/authz0

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

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:authz0
Version1.1.2
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/authz0
Homepagehttps://authz0.hahwul.com/
Repositoryhttps://github.com/hahwul/authz0
Upstream-Dokumentationhttps://authz0.hahwul.com/
LizenzMIT
Quellarchivhttps://github.com/hahwul/authz0/archive/refs/tags/v1.1.2.tar.gz
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

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

Nix95%

authz0

nix profile install nixpkgs#authz0
  • normalized package name match
  • Abgeglichen nach: Authz0
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/au/authz0/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