Skip to main content

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

  1. Go to github.com/settings/tokens/new (classic) or github.com/settings/tokens (fine-grained)
  2. Select the required scopes:
    • repo — full access (required for private repos and opening PRs)
    • public_repo — public repos only (read-only scanning)
  3. 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):
  1. Clones the target repository
  2. Redacts the secret value in-place with a <REDACTED_*> placeholder
  3. Opens a PR with a description linking to the finding and remediation steps
  4. You review and merge — no manual patching
For .gitignore findings:
  1. Opens a PR that adds the missing .env* exclusion pattern
  2. No secrets are modified — only .gitignore is updated
For other findings:
  1. Generates an AI fix
  2. 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:
This is useful as a CI step: it creates a clean-up PR when the scan finds only low-severity issues, keeping your security debt from accumulating.

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

Set these at Settings → Secrets and variables → Actions in your repository.

Exit codes for CI gates