gha-security-review

Identifies exploitable vulnerabilities in GitHub Actions workflows by tracing attack paths.

Updated May 5, 2026
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill gha-security-review-iani-kuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gha-security-review
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/ported/gha-security-review
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill gha-security-review-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the critical risk of supply chain attacks and unauthorized code execution within GitHub Actions workflows by identifying exploitable patterns like expression injection, credential theft, and pwn requests.

Core Features & Use Cases

  • Attack Path Tracing: Analyzes workflows to confirm if vulnerabilities are actually exploitable by external attackers.
  • Vulnerability Classification: Detects dangerous patterns such as pull_request_target misuse, expression injection in run blocks, and unpinned third-party actions.
  • Use Case: Before merging a pull request that modifies CI/CD pipelines, use this skill to ensure that no new workflow changes introduce vulnerabilities that could lead to secret leakage or repository compromise.

Quick Start

Run the gha security review skill on the current repository to audit all workflow files for potential exploitation vectors.

Frequently Asked Questions about gha-security-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit GitHub Actions workflows for security vulnerabilities?

Audit GitHub Actions workflows for security vulnerabilities by tracing attack paths from external triggers to sensitive execution points, validating high and medium confidence findings with concrete exploitation scenarios.

How does expression injection in CI/CD pipelines work?

Expression injection in CI/CD pipelines occurs when untrusted input from external triggers is evaluated in run blocks, allowing attackers to execute unauthorized code or steal credentials within GitHub Actions workflows.

Can I check if pull_request_target misuse leads to secret leakage in my repository?

Yes, you can check for pull_request_target misuse by analyzing workflow YAML configurations to trace if external attackers can reach sensitive execution points and exploit credential escalation paths.

Does this security review detect unpinned third-party actions and supply chain poisoning risks?

Yes, this security review detects unpinned third-party actions and supply chain poisoning risks by evaluating dangerous patterns within .github/workflows and local action definitions for exploitable attack vectors.

When should I run a GitHub Actions security audit on my DevSecOps pipeline?

Run a GitHub Actions security audit before merging a pull request that modifies CI/CD pipelines to ensure no new workflow changes introduce vulnerabilities that could lead to secret leakage or repository compromise.