Keep CI from becoming an entry point.
Spot privileged PR checkouts, mutable action references, missing token permissions, and event expressions interpolated into shell scripts.
workflow/pwn-requestCatch risky workflows, configuration drift, and leaked credentials from your terminal, CI pipeline, or AI assistant.
$ npx ci-guard-mcp scan . .github/workflows/deploy.yml:8 ERROR workflow/script-injection Untrusted event data in a shell script. Pass it through a quoted env variable. src/config.ts:12 WARN env/undocumented API_URL is absent from an env template. → 2 findings. No source uploaded. Illustrative output · values redacted
Concrete findings with file locations, rule IDs, and a suggested next step. No account or cloud scanner required.
Spot privileged PR checkouts, mutable action references, missing token permissions, and event expressions interpolated into shell scripts.
workflow/pwn-requestCompare literal environment reads across JS/TS, Python, Go, and Rust against templates, Docker ENV, and Compose declarations.
env/undocumentedRecognize common token formats, private keys, and contextual high-entropy assignments. Scan actual staged blobs and redact every detected value.
secret/high-entropyFind competing lockfiles within a package, unencrypted dependency URLs, and unbounded version selectors such as * and latest.
lockfile/conflictRun directly via npx in your terminal, wire the composite action into GitHub Actions CI, or connect over stdio MCP.
Audit any repository in text, JSON, SARIF 2.1.0, or GitHub annotations format.
npx ci-guard-mcp scan . \ --fail-on warn npx ci-guard-mcp scan . \ --format sarif > findings.sarifCLI usage ↗
Annotations, a readable job summary, and finding counts from a composite action.
- uses: carelessdept/ci-guard-mcp@release-0.1.0
with:
path: .
fail-on: warnIntegration details ↗Four read-only tools over stdio. Paths stay within the selected launch root.
npx -y ci-guard-mcp --mcp \ --root /path/to/repo # scan_repo # check_secret_leaksMCP configuration ↗
Static checks cannot prove a repository is safe. Dynamic environment reads, encoded credentials, and remote workflow bodies need other review. Test fixtures and templates are excluded from secret scanning by default.
Read the detection limits ↗