Overview
ZenVeil has deep GitHub integration — scan any repository, automatically remediate findings with pull requests, and add security gates to your CI/CD pipeline.Scanning GitHub repositories
Setting up a GitHub token
- Go to github.com/settings/tokens/new (classic) or github.com/settings/tokens (fine-grained)
- Select the required scopes:
repo— full access (required for private repos and opening PRs)public_repo— public repos only (read-only scanning)
- Set it as an environment variable:
Auto-PR: fix and ship
The most powerful ZenVeil feature — generate a fix and open a GitHub PR automatically.What auto-PR does
For secret findings (AWS keys, GitHub tokens, Slack tokens, JWT tokens):- Clones the target repository
- Redacts the secret value in-place with a
<REDACTED_*>placeholder - Opens a PR with a description linking to the finding and remediation steps
- You review and merge — no manual patching
.gitignore findings:
- Opens a PR that adds the missing
.env*exclusion pattern - No secrets are modified — only
.gitignoreis updated
- Generates an AI fix
- Opens a PR with the fix in the description for you to apply manually
Auto-PR for low-severity findings
After scanning a GitHub repo, automatically open a PR if all findings are LOW:GitHub Actions integration
Basic security gate
Block merges if CRITICAL or HIGH findings are detected:Scan with CVE checks
Auto-fix PRs in CI
Secrets required in GitHub
| Secret name | Value |
|---|---|
ZENVEIL_API_KEY | Your ZenVeil API key from the dashboard |
GITHUB_TOKEN | Auto-provided by Actions, or a PAT with repo scope |
ANTHROPIC_API_KEY | Required for explain, fix, triage commands |