If you discover a security vulnerability in this project, please report it responsibly.
Do not open a public issue. Instead, email the maintainer or use GitHub's private vulnerability reporting.
This project contains GitHub Actions reusable workflows that invoke Claude via claude-code-action@v1.
Security concerns include:
- Prompt injection: Issue/PR content passed to Claude via prompt templates — an attacker could craft issue titles or PR descriptions to manipulate Claude's behavior
- Permission escalation: Workflows requesting broader permissions than needed for their task
- Secret exposure: Accidental leakage of
CLAUDE_CODE_OAUTH_TOKEN - Fork safety: The CI Fix workflow has an explicit fork guard to prevent untrusted code checkout in the privileged
workflow_runcontext - OIDC token misuse: Workflows use
id-token: writefor OIDC token exchange — this should not be granted beyond what's needed
- All workflows use minimal permissions — each job declares only what it needs
- Secrets are never committed; workflows reference
${{ secrets.* }} - Commit signing uses GitHub's native App signing via
use_commit_signing: "true"inclaude-code-action@v1, not long-lived PATs - OIDC token exchange (
id-token: write) replaces long-lived API key auth - Fork guard in ci-fix.yml prevents processing untrusted fork branches in the
workflow_runcontext - Dependency bot runs (Renovate, Dependabot) are filtered via
if:actor guards on gate-check jobs, producing clean skipped status instead of failures