google-github-actions / google-github-actions/run-gemini-cli
Consent request: lightweight AI workflow safety review
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.1k
- Forks
- 285
- Avg merge
- 8h 8m
- Merged PRs (30d)
- 1
Description
Hi maintainers,\n\nI maintain gentic-actions-guard, a small OSS scanner for AI/agent GitHub Actions workflow boundaries: https://github.com/sho-tado/agentic-actions-guard\n\nI'm doing consent-first reviews of public AI GitHub Actions workflows. The review looks only at public workflow files and focuses on maintainer-safety boundaries such as untrusted GitHub event input, secrets, token permissions, pull_request_target, checkout credentials, mutable AI action refs, and AI output flowing into shell execution.\n\nWould you be open to receiving a lightweight Markdown review report for this repository's public workflows?\n\nIf yes, I'll share a concise report in this issue or wherever you prefer. If not, no worries, I will not post repo-specific findings.\n\nI will not include secrets, private prompts, exploit payloads, or non-public repository content.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or code entry point is identified. First confirm whether maintainers want a Markdown review of public GitHub Actions workflow files; if accepted, done would be a concise report covering the listed safety boundaries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100