Skip to main content

Actions Warden

Read-only auditor for risky or injected GitHub Actions workflow config.

Current release: 0.1.5

After the 2026 wave of repository-theft attacks, a common post-compromise move is: steal a token, then inject or tamper with a repo's .github/workflows/ so CI exfiltrates secrets or runs attacker code. Actions Warden scans those workflow files for the patterns that enable it.

It does not execute workflows, contact GitHub, modify files, or prove a pipeline is safe. No telemetry, no data storage, no automatic remediation — alerts only.

Part of the Dragon Lady open security kit used alongside package/host scanners during the August 2026 npm/keyv (ChainDrop / Shai-Hulud) emergency tooling updates: when tokens may have been stolen, also audit CI workflows.

Install

pipx install actions-warden
# or
pip install actions-warden
# upgrade:
pipx upgrade actions-warden
# or: pip install -U actions-warden

Python 3.9+. No runtime dependencies.

Usage

actions-warden --version
actions-warden /path/to/repo
actions-warden /path/to/repo --json
actions-warden /path/to/repo --report report.json

It scans .github/workflows/*.yml|*.yaml and composite action.yml|action.yaml files. You can also point it at a single workflow file.

Exit codes:

  • 0: no blocking workflow risks found
  • 1: usage/runtime error or incomplete scan
  • 2: blocking workflow risks found (suitable as a CI gate)

Missing or unsupported targets fail explicitly. Unreadable files/directories, invalid text, and candidate size limits set coverage.complete: false with path/reason entries in coverage.errors. Blocking findings still return 2; otherwise incomplete scans return 1, never 0. Completeness covers only the scanner's selected file types and directory policy, not every repository file.

--report creates a new report exclusively (mode 0600 on POSIX). Existing files, symlinks and hard links are refused, including aliases of scanned inputs. Write failures return 1; a partial newly created report may remain and must not be treated as a successful result. Choose a fresh output path for each run.

What It Flags

Rule Severity What it catches
secret-exfiltration critical a secret reference alongside an outbound network command
untrusted-input-injection high attacker-controllable github.event.* / head_ref interpolated into the workflow (shell injection in run steps)
remote-code-in-run high a downloaded script piped straight into a shell
pull-request-target-head-checkout high pull_request_target running with secrets while checking out PR-controlled code ("pwn request")
checkout-unsafe-pr-opt-out high actions/checkout explicitly setting allow-unsafe-pr-checkout on privileged PR-adjacent triggers
self-hosted-on-untrusted medium self-hosted runner reachable by external pull requests
permissions-write-all medium write-all token permissions
oidc-with-write medium OIDC id-token: write combined with contents: write
deployment-trigger-review medium workflows triggered by deployment / deployment_status that need GitHub workflow execution protections reviewed
deployment-trigger-privileged high deployment-triggered workflows that also reference secrets, OIDC, or write permissions
unpinned-action low third-party action pinned to a mutable tag/branch instead of a commit SHA
hijacked-actions-cool-tag critical actions-cool/issues-helper or actions-cool/maintain-one-comment on a tag, branch, or the known hijacked commit. Stop using the tag. Do not revoke tokens until the monitor and wiper are understood
memtensor-sckit-stage0 critical workflow text contains both sckit and stage0. Treat the runner and publish tokens as exposed. Do not run the step. Notify-only

The rules are conservative. A finding means "review this workflow," not "this repo is compromised."

GitHub announced safer actions/checkout@v7 defaults for common pull_request_target pwn-request patterns on 2026-06-18, with supported major tag backports planned for 2026-07-16. Workflows pinned to a minor, patch, or full SHA need an explicit upgrade to receive that behavior, and any allow-unsafe-pr-checkout opt-out should be treated as a deliberate high-risk review item.

GitHub's workflow execution protections public preview also lets organizations restrict which actors and event types can trigger workflows. Treat deployment / deployment_status workflows as review items, and treat deployment-triggered workflows that use secrets, OIDC, or write permissions as blocked until the repository or organization restricts that trigger.

Why text-based, not YAML-parsed

A hostile workflow can be written to parse in surprising ways. Actions Warden inspects what is actually on disk rather than a parser's normalized view, and stays dependency-free. The tradeoff is coarser context: some file_all rules flag co-occurrence within a file rather than within a single job.

Scope Limits

This is a narrow CI/CD config scanner. It does not scan dependencies or packages (see a dependency/supply-chain scanner for that), does not resolve reusable or remote workflows, and will not catch every possible injection or obfuscated payload.

Metadata

Release files for actions-warden 0.1.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for actions-warden 0.1.5
File Size Uploaded Provenance Actions
actions_warden-0.1.5.tar.gz 17.9 kB With provenance Details for actions_warden-0.1.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for actions-warden 0.1.5
File Interpreter ABI Platform Actions
actions_warden-0.1.5-py3-none-any.whl Python 3 none any Details for actions_warden-0.1.5-py3-none-any.whl

Total release size: 31.4 kB

Release files / actions_warden-0.1.5.tar.gz

Download URL actions_warden-0.1.5.tar.gz
Size 17.9 kB
Tags Source
SHA-256 checksum
How to use checksums
23edf0a9ad97bb65054a2db2a90c93aea022a89439a5bb00c3a8f0af4c37422d
BLAKE2b-256 checksum
How to use checksums
0eadd6af30904916f04c0c50b637315b9344e945174bcd39df94e7c32f62d1ea
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Release files / actions_warden-0.1.5-py3-none-any.whl

Download URL actions_warden-0.1.5-py3-none-any.whl
Size 13.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
4d9cc35f9d0140e2347162c86c6216e32b2487a2c438b894b5a1368e4bf93c31
BLAKE2b-256 checksum
How to use checksums
71a31bd315c09305dbf9a49725de0577d663b2e53a45d8ba93c99985da1e5067
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

Security for actions-warden 0.1.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for actions_warden-0.1.5.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 16, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page