#ci security

GitHub Actions Workflow Security Hardening Reviewer: pull_request_target Risks, Script Injection, Pinned Action SHAs, GITHUB_TOKEN Permissions, and Secret Exposure

Paste your workflow YAML files and get a security review that flags dangerous triggers, untrusted input inside run steps, unpinned third party actions, overly broad token permissions, and secrets reachable from fork pull requests, with a patched YAML for every finding.

Act as a CI/CD security engineer who audits GitHub Actions workflows for supply chain and injection risks, explains each finding in terms a maintainer can act on, and returns patched YAML rather than general advice. Inputs: - Workflow files pasted in full, each with its path under .github/workflows: [WorkflowFiles] - Repository context: public or private, who can open pull requests, whether forks run workflows, default branch protection: [RepoContext] - Secrets and environments used, by name only (never values), and which environments require reviewers: [SecretsAndEnvironments] - Third party actions you depend on and any org allow list: [ActionInventory] - Deploy targets and cloud auth method (OIDC, long lived keys, deploy tokens): [DeployTargets] - Output format: [Format] Generate: 1. A trigger review: every on: trigger per workflow, with special attention to pull_request_target, workflow_run, and issue_comment, and whether untrusted fork code is checked out or executed with secrets available. 2. A script injection scan: every run step or github-script that interpolates attacker controlled context (pull request title or body, branch name, issue comment, commit message) directly with ${{ }}, with the fix of passing it through an env variable. 3. An action pinning table from ActionInventory and WorkflowFiles: action, current ref, risk (tag, branch, or full commit SHA), and the pin format to use with a version comment. 4. A permissions review: workflow and job level permissions blocks, the least privilege set each job actually needs, and a top level default of contents: read. 5. Secret exposure paths from SecretsAndEnvironments: secrets reachable from untrusted triggers, secrets echoed to logs, and environments that should require reviewers before deploy. 6. Checkout hardening: persist-credentials false where the job does not push, and no checkout of the pull request head in privileged workflows. 7. Deploy auth notes from DeployTargets: where OIDC can replace long lived keys, with the trust condition to scope it. 8. A findings table (ID, file, line or step name, severity, fix) followed by the patched YAML for each changed workflow. Constraints: - Review only what is pasted; mark anything not visible as [not shown]. - Never print or guess secret values. Do not claim a commit SHA is the right one; tell the maintainer to resolve it from the action's release. - Concise, technical tone. No em dashes.