github-actions[bot]
published Jul 7, 2026, 9:47 PM · updated Jul 7, 2026, 9:47 PM
Daily Runtime Threat Scan
Verdict: CLEAN
The setup/ action is consistent with a legitimate GitHub Actions setup/install action. All observed behaviors are expected:
- File operations: Copies bundled .cjs/.sh/.json files to $RUNNER_TEMP/gh-aw/actions — standard pattern for setup actions.
- Network activity: Limited to user-configured OTLP endpoints, localhost health checks, official GitHub release downloads (with SHA256 verification), and the official GitHub CLI source. No hardcoded suspicious endpoints.
- Token handling: Tokens are passed only to Docker containers and git operations — no exfiltration to third-party services.
- Cleanup: post.js removes only /tmp/gh-aw/ and chroot directories created by the action itself.
- Unexpected files: .bak test file and .prettierrc are benign development artifacts; Docker/TypeScript/vitest configs are normal for a JavaScript-heavy action.
- No red flags: No obfuscation, no persistence mechanisms, no cryptocurrency patterns, no encoded payloads.
The action's scope and behavior align with the gh-aw project's documented purpose of managing agentic workflow infrastructure on GitHub-hosted runners.
Generated from Daily Runtime Threat Scan · 688.1 AIC · ⊞ 36.4K · ◷