Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for teams already standardizing on GitHub Actions: evaluate it on a low-risk repository to see whether agent workflows can automate triage, code-review chores, or release checks without introducing a separate agent platform.
Who should use it
Who should skip it
Move on from github/gh-aw (GitHub Agentic Workflows) if the licensing terms, language support, or platform requirements do not fit your project.
About this signal
github/gh-aw (GitHub Agentic Workflows) is tracked by RepoRadar as a developer tool in the Developer Tools section. First seen 2026-06-16; the source record was last checked on 2026-06-16. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. github/gh-aw (GitHub Agentic Workflows) leads on workflow potential (9.9) and practical usefulness (9.0); its lowest signal is setup ease (6.4), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.
How this item is evaluated
The github/gh-aw (GitHub Agentic Workflows) record combines a 8.4/10 composite score with separate popularity (86.0), risk (conditional), and setup (moderate) signals. See the scoring methodology for the current weights and evidence definitions.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
can operate inside repositories and CI workflows; misconfigured workflow permissions could expose code or secrets.