Security Designed for Zero-Trust Codebases
Connecting a bot to your GitHub repositories requires absolute trust. Here is every technical control we enforce so your code stays yours.
Zero Source-Code Retention
Your repository is streamed strictly into ephemeral in-memory RAM (/tmp tmpfs) during a scan and wiped immediately in a finally block. Our Postgres database never stores source code.
Code-Redacting Structured Logs
Our engine logger explicitly strips source lines, diffs, and tokens before writing to Google Cloud Logging—so customer code never leaks into 30-day log retention.
1-Hour Scoped GitHub App Tokens
We never ask for personal access tokens. GitHub App installation tokens expire every 60 minutes and are scoped only to Contents (R/W) and Pull Requests (R/W) on selected repos.
Deterministic Prompt-Injection Diff Firewall
External API specs are treated as untrusted data. Before any PR opens, deterministic code blocks patches touching unmatched files, .github/workflows/, .env files, eval(), or unapproved URLs.
SSRF-Hardened Spec Fetcher & Isolated IAM
Custom OpenAPI URLs block metadata.google.internal, 169.254.169.254, private IPs, and non-HTTPS schemes. The public web service has zero IAM access to repos or Vertex AI.