self-hosted-github-runner
Pass
Audited by Gen Agent Trust Hub on Sep 20, 2026
Risk Level: SAFECOMMAND_EXECUTIONEXTERNAL_DOWNLOADSDATA_EXFILTRATIONINDIRECT_PROMPT_INJECTION
Full Analysis
- [COMMAND_EXECUTION]: The skill provides various shell commands for local environment analysis and GitHub runner management.
- Uses
gh apiandgh run listto query GitHub Actions status and metadata. - Uses
docker runto execute performance benchmarks and architecture checks (node,ldd). - Uses shell scripting (
case,uname -m) to handle multi-architecture deployments safely. - [EXTERNAL_DOWNLOADS]: The skill references and utilizes external software components.
- Recommends the use of
myoung34/github-runner:latest, a third-party Docker image widely used for self-hosted runners. - Mentions
nektos/actas an alternative tool for local workflow execution. - Mentions
gitleaksas an example for architecture-aware installation logic. - [DATA_EXPOSURE]: The skill handles sensitive GitHub Actions registration tokens.
- Implementation includes security best practices: writing the token to a temporary file with
chmod 600permissions and immediately deleting it after use to prevent exposure indocker inspector shell history. - [INDIRECT_PROMPT_INJECTION]: The skill identifies and warns about the risk of executing untrusted code via GitHub Actions.
- Ingestion points: The runner processes code, dependencies, and scripts provided in GitHub Pull Requests (
SKILL.md). - Boundary markers: The skill explicitly warns that "the risk is not who opens the PR, but what code that job executes," and suggests using manual triggers or tags to mitigate risks.
- Capability inventory: The runner executes arbitrary shell commands defined in workflows, potentially with access to the host via
docker.sockif configured by the user (SKILL.md). - Sanitization: No automated sanitization is performed, as the intended purpose is to run the provided workflow code; the skill relies on user-initiated process isolation.
Audit Metadata