zanadir

zanadir is an open-source CI/CD security tool. It reads a repository's pipeline, from GitHub Actions to GitLab CI, and reports which security and quality checks are missing, or wired so they cannot fail a build.

What it answers

• What is my pipeline missing? Thirteen categories, from dependency scanning and secrets detection to SBOMs, workflow hardening and agent skill scanning, each checked against the tools that cover it, with suggestions that fit the repository's languages.
• Does my CI actually block on security findings? A scanner with continue-on-error, || true, a push-only trigger or allow_failure, or one that only reports unless told to fail, like trivy without --exit-code 1, is present but cannot stop a merge. zanadir grades each control *enforcing*, *partial*, *advisory* or *unknown* rather than just covered; see Effectiveness.
• Is that check required to merge? With --required-checks, a control only counts as enforcing when branch protection or a ruleset requires it.
• What do I add? zanadir fix prints ready-to-paste CI configuration for the gaps, or writes a workflow with --write.

It reads GitHub Actions, GitLab CI, CircleCI, Bitbucket Pipelines, Azure Pipelines and Jenkins, from a checkout (--dir) or straight from GitHub (--repo), and reports as a table, JSON, SARIF or Markdown. To see it on a public repository first, scan it in your browser. For how it maps to the OWASP Top 10 CI/CD Security Risks, and how it differs from OpenSSF Scorecard, see the mapping and the comparison.

How common are these gaps? The State of CI security 2026 scanned 1,000 of the most-starred GitHub repositories: 511 declare no dependency, secret or code scanning at all, and 1 in 6 of those that run a scanner in CI have one that cannot fail the build.

zanadir scan --dir .

zanadir scan --repo github.com/owner/name --output json zanadir fix --dir .

Installation

Try it on any public repository without installing anything, in your browser at mustachecase.github.io/scan (zanadir runs there as WebAssembly, and the repository's files never leave your browser), or with Docker:

docker run --rm mustachecase/zanadir scan --repo github.com/owner/name

To install it, download the archive for Linux, macOS or Windows (amd64 or arm64) from the latest release. checksums.txt lists each archive's SHA-256, and every archive has a build provenance attestation:

gh attestation verify zanadir_<version>_linux_amd64.tar.gz --repo MustacheCase/zanadir

Or with Homebrew (the tap is this repository) or Go:

brew tap --custom-remote MustacheCase/zanadir https://github.com/MustacheCase/zanadir.git

brew install mustachecase/zanadir/zanadir go install github.com/MustacheCase/zanadir@latest

In GitHub Actions, use zanadir-action. This workflow reports on every pull request without failing it:

# .github/workflows/zanadir.yml

name: zanadir on: [pull_request] permissions: contents: read jobs: zanadir: runs-on: ubuntu-latest steps:

• uses: actions/checkout@v4 with: fetch-depth: 0
• uses: mustachecase/zanadir-action@v1.40 with: dir: .

When you are ready to gate, add enforce: true (fail on any uncovered category), fail-on (only the categories you name) or fail-on-weakened. To post the report as a pull request comment, see Posting the report to a pull request.

zanadir and OpenSSF Scorecard

OpenSSF Scorecard and zanadir answer different questions, and work well together.

Use Scorecard for a project-wide security posture, and zanadir to find out whether the CI you have would actually stop a bad change, and what to add.

Using zanadir with AI coding agents

To have a coding agent check CI with zanadir before changing it, add this to the repository's AGENTS.md, CLAUDE.md or equivalent:

## CI changes

Before adding or changing CI configuration, run zanadir scan --dir . --output json (install: https://github.com/MustacheCase/zanadir#installation). It lists the missing CI controls and grades each present one: enforcing can fail a merge, partial, advisory and unknown cannot or may not. Fix advisory controls before adding tools, and use zanadir fix --dir . for configuration that fits this repository. Re-run the scan to confirm the change.

As an MCP server

zanadir mcp serves three read-only tools over the Model Context Protocol, so any agent that speaks MCP can grade CI, and check agent skills, before and after changing them:

• scan returns the JSON report: the score, uncovered categories with suggested tools, and weakened controls with their verdicts;
• fix returns ready-to-paste configuration for the gaps, and writes nothing;
• skills returns zanadir skills' JSON: the skills found and their problems.

Each takes dir (a local checkout, by default the current directory) or repo (github.com/owner/name[@ref], read without cloning); scan and fix also take excludedCategories.

An agent can be steered by what it reads, so the server keeps its tools to what you started it with. A dir must be inside --dir (by default the directory the server starts in); a relative one is read from there. repo fetches are anonymous, so they reach public repositories only, unless you start the server with --repo-token to let them use GITHUB_TOKEN or GH_TOKEN.

claude mcp add zanadir -- zanadir mcp

It is listed in the MCP Registry as io.github.MustacheCase/zanadir, where it runs from the Docker image with your repository mounted read-only. For other clients, such as Cursor, VS Code or Windsurf:

{

"mcpServers": { "zanadir": { "command": "zanadir", "args": ["mcp"] } } }

As a Claude Code plugin

In Claude Code, the zanadir plugin brings both: the MCP server, and a skill that scans, reads your CI configuration, recommends fixes in priority order, and edits files only after you choose. The server runs the installed zanadir if it is 0.18.0 or later, and otherwise the Docker image.

/plugin marketplace add MustacheCase/zanadir

/plugin install zanadir@mustachecase

Then ask Claude Code to review or harden your CI, or run /zanadir:improve-ci.

llms.txt summarises zanadir for agents that read the repository, and is served at mustachecase.github.io/llms.txt for those that look at a site's root.

Features

• 📂 Scan: Analyze the repository for CI/CD enhancement suggestions, including security services and best practices.
• 🔍 CI Analysis: Grades whether each control can actually fail a build, not only whether it is present.
• 🛠️ Fix: Prints, or writes as a workflow, CI configuration for the categories a scan reports as missing.
• 🚀 Open Source: Contributions are welcome to enhance Zanadir's capabilities!

Supported CI Actions

Zanadir currently supports:

• GitHub Actions
• CircleCI
• GitLab
• Bitbucket Pipelines
• Azure Pipelines
• Jenkins

Future work will include support for:

• Tekton

Categories We Suggest

Zanadir analyzes repositories in the following categories. The name in bold is the exact value to pass to --excluded-categories (matching is case-insensitive):

• 🛡️ SCA: Software Composition Analysis
• 🔐 Secrets Detection: Secrets Management
• 📜 License Compliance: License Compliance
• 🛠️ End Of Life: End-of-Life Software Packages
• 📊 Coverage: Test Coverage
• 📊 Performance Testing: Test Performance and Reliability
• 🧑💻 Linter: Code Linting
• 🧪 Unit Tests: Automated Unit Testing
• 🔎 SAST: Static Application Security Testing
• 🏗️ IaC Security: Infrastructure-as-Code Misconfiguration Scanning
• 🔗 Supply Chain: SBOM Generation, Signing and Provenance
• 🧱 Workflow Security: Hardening of the pipeline definition itself
• 🤖 Agent Skill Security: Scanning agent skills (SKILL.md) for prompt injection and malicious code

Usage Examples

Basic Usage

Scan a repository for CI/CD improvement suggestions:

zanadir scan --dir /path/to/your/repo

Or scan a GitHub repository without cloning it:

zanadir scan --repo github.com/owner/name

zanadir scan --repo owner/name@v2.0.0 # a branch, tag or commit zanadir fix --repo owner/name

--repo lists the repository's files at one commit and downloads only the ones zanadir reads (CI and build files, plus the start of JSON files for infrastructure detection) into a temporary directory. Every other file is an empty placeholder, since only its name matters. It then scans the directory exactly as a checkout and removes it. That is three GitHub API requests per scan, however large the repository. A repository too large to list in one request is downloaded as an archive instead. Public repositories need no token; set GITHUB_TOKEN (or GH_TOKEN) to reach private ones or raise GitHub's rate limit of 60 requests an hour without one. GitLab and Bitbucket repositories still need a clone.

Output Formats

Zanadir supports three output formats: table (default), JSON and SARIF.

Table Output (Default)

zanadir scan --dir . --output table

Sample Output:

Coverage 10/11 - 1 category needs attention:

|--------------------------------|--------------------------------|-------------------| | CATEGORY | DESCRIPTION |