Gha Security Review

What it does

The source distinguishes external attackers from repository writers and routes findings through trigger classification and concrete attack paths. It covers fork checkout under elevated events, expression injection, comment-triggered commands, poisoned configuration and third-party action references.

Best for

Reviewing CI workflows that may process pull requests, issues or other data supplied by people without repository write access.

Tradeoffs and requirements

The threat model intentionally excludes some risks that require trusted-writer access. That boundary must be stated rather than interpreted as universal safety. A workflow file alone may not reveal reusable actions, scripts, runner settings or organization-level protections.

Unknown; inspect source requirements and supporting scripts.

Install from the source

Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.

npx skills add https://github.com/getsentry/skills/tree/d12f250460ffd961f549dbebf7eeb0cf4afd4c2e/skills/gha-security-review --skill gha-security-review

Review pinned skill folder ↗ · CLI documentation ↗

After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.

Safety & review signals

Static review only. This is not a security audit or a guarantee of safety.

SKILL.md text only; scripts, dependencies and runtime behavior not audited.

• Credential Reference — review the source context.
• Network Access — review the source context.

Allowed tools declaration: Read Grep Glob Bash Task. Runtime permissions and network behavior: Unknown.

AI Craft Pad Skill Score

86/100 · Metadata coverage 100% · Model 1.0

Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.

Documentation

100/100

100

Maintenance

100/100

100

License Clarity

100/100

100

Repository Health

100/100

100

Compatibility Evidence

80/100

80

Popularity

55/100

55

Originality

80/100

80

Static Safety

60/100

60

Suggested workflow

Identify each event and trust boundary, follow the checkout and data paths into commands, and inspect the exact referenced actions. Establish whether attacker-controlled content can reach a privileged operation.

How to judge the result

Support each reported issue with a plausible controlled-input path and its required conditions. Test safely in an isolated fixture where practical, and document dependencies or infrastructure settings that could not be inspected.