pkg.sopackage field notes

brew / rank 677

Install zizmor with Homebrew

Find security issues in GitHub Actions setups. Version 1.29.0 via Homebrew; verified 2026-08-01.

install

Additional install commands

macOS

Homebrewverified ยท 100%
brew install zizmor

provider-native install command

overview

Package summary

Find security issues in GitHub Actions setups

Commands and aliases

  • zizmor

history

Project history and usage

zizmor is a static-analysis tool for GitHub Actions workflows and actions. It belongs to the newer supply-chain-security wave: instead of scanning application source code, it scans CI/CD definitions for patterns that can leak credentials, allow injection, over-grant permissions, or otherwise compromise releases.

Project history

The project documentation describes zizmor as a tool that can find and fix common security issues in GitHub Actions CI/CD setups. The README lists examples including template-injection vulnerabilities, accidental credential persistence and leakage, excessive permission scopes, and confusable Git references.

zizmor reached a first stable release with v1.0.0, where the official release notes state that the project adopted Semantic Versioning and made stability commitments for existing features. Since then, the project has continued adding audits, output modes, auto-fix behavior, and integrations.

The project also grew a companion GitHub Action. `zizmor-action` runs zizmor inside CI and can integrate with GitHub Advanced Security by uploading findings to code scanning, turning the CLI into a recurring workflow check.

Adoption history

zizmor's adoption tracks the rise of GitHub Actions as release infrastructure and the resulting need to audit workflows as security-sensitive code. Its documentation includes integrations for GitHub Actions, pre-commit, IDEs, and other environments, while the sponsor list includes Grafana Labs, Trail of Bits, Kusari, and Tracebit.

The official trophy case documents examples where zizmor helped larger projects improve GitHub Actions security. That is a strong adoption signal for this niche because the tool's value is demonstrated through pull requests that harden real workflows rather than through a generic scanner benchmark.

Trail of Bits' 2026 work on YAML-anchor support shows zizmor moving with the GitHub Actions platform itself: when Actions added YAML anchors, the analyzer had to understand that syntax to keep coverage over modern workflow files.

How it is used

Users run `zizmor` against workflow files, action definitions, directories, or repositories. The quickstart documents inputs, collection modes, severity and confidence filtering, multiple output formats including JSON, SARIF, and GitHub annotations, and an experimental `--fix` mode.

The usage docs emphasize its static nature: zizmor analyzes workflow and action definitions without executing code or observing runtime state. This makes it suitable for local checks, pre-commit hooks, CI jobs, and code-scanning uploads, while still requiring users to understand runtime-only limitations.

Why package nerds care

zizmor is package-nerd significant because it treats CI configuration as a first-class supply-chain artifact. For maintainers, installing it is a low-friction way to audit the same YAML that builds, signs, publishes, and deploys packages.

It is also a good example of modern security tooling packaging: a Rust CLI, documentation-first audit catalog, machine-readable outputs, and a GitHub Action wrapper that lets projects consume the tool either locally or as part of repository security automation.

Timeline

  • 2024: zizmor documentation copyright begins under William Woodruff, matching the project's early public documentation era.
  • 2025: v1.0.0 is identified in official release notes as the first stable release with Semantic Versioning.
  • 2025: The GitHub Marketplace lists zizmor-action as a public action for running zizmor in workflows.
  • 2026: Trail of Bits collaborates with zizmor maintainers to harden YAML-anchor support after GitHub Actions adds anchors.

Related projects

  • zizmor-action, the official GitHub Action wrapper for running zizmor in CI.
  • GitHub Advanced Security code scanning and SARIF-based workflows.
  • pre-commit, IDE integrations, Scorecard, OSSF/SLSA-adjacent supply-chain hardening tools, and GitHub Actions security guidance.

security posture

No protected-tool coverage found yet

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

Install behavior

  • No Homebrew bottle metadata was recorded.

Recommended review

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

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
zizmor.ymlzizmor.yaml

executables

Installed executables

CommandKindExposureNote
zizmorexecutableindexed executableDiscovered from the local executable index.

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-08-03
manager version1.29.0
manager updated2026-08-01
local dataunknown
upstreamnot available
latest detectednot detected
  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:zizmor
Version1.29.0
Package managerHomebrew
Homepagehttps://docs.zizmor.sh/
Repositoryhttps://github.com/zizmorcore/zizmor
Last updated2026-08-01T22:00:29Z
Pulseupdated
Bottlenot recorded
Servicenone declared

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
  • curated configuration and credential file locations
  • curated package history
  • pkgdb category and tag curation