An AI-powered security gate for Git. Every time you run git commit, CommitGate scans the staged diff for potential vulnerabilities and blocks the commit before secrets or risky code ever reach your history.

It runs two scanners over your staged changes and merges their findings:

Findings from both layers are merged, deduplicated, and fed into a decision engine that rules allow / warn / block. A Rich terminal report explains why.

Demo

CommitGate blocking a vulnerable commit before it reaches Git history.

Table of Contents

• Setup
• Usage
• How it works
• Splunk Setup
• Module map
• Data Privacy
• License

Setup

1. Install prerequisites

Install these on your machine before installing CommitGate:

• Python ≥ 3.10

• Git

• Gitleaks — an external binary that must be installed separately (it is not pulled in by pip):

  • Windows: winget install gitleaks
  • macOS: brew install gitleaks
  • Linux: download the release binary and place it on your PATH

  Confirm it's on your PATH before continuing:

• AI API key — required for the AI reviewer (pick one provider; you'll add the key to your .env in step 3):

  • Groq — free tier available, recommended for getting started
  • DeepSeek — low cost
  • OpenAI
  • Gemini

2. Install CommitGate

pip install git+https://github.com/ductrl/CommitGate.git

3. Configure environment variables

Create a .env file in the root of your project (not CommitGate's repo):

# Required — AI reviewer (one key for whichever provider you set in commitgate.yaml)
AI_KEY=your-api-key-here
# Free option: get a Groq key at https://console.groq.com, then set provider: groq in commitgate.yaml

# Optional — AI review timeout in seconds (default: 20)
# COMMITGATE_AI_TIMEOUT=20

# Optional — Splunk audit logging (see Splunk Setup below)
# SPLUNK_HEC_TOKEN=your-hec-token-here
# SPLUNK_HEC_URL=https://prd-p-yourinstance.splunkcloud.com:8088/services/collector/event
# SPLUNK_VERIFY_SSL=false                   # required for Splunk Cloud free trial

.env should be gitignored — your keys should never enter source or git history.

4. Initialize CommitGate

Run this inside the repo you want to protect:

This does two things at once:

• Creates a commitgate.yaml config file in the repo root
• Writes .git/hooks/pre-commit so commitgate scan fires automatically on every commit

The generated commitgate.yaml looks like this — edit it to match your needs:

ai:
  enabled: true          # set to false to run gitleaks only (no API key needed)
  # Options: openai, deepseek, gemini, groq
  # Tip: groq offers a free API key — get one at https://console.groq.com
  provider: deepseek
  timeout: 20            # seconds before AI review is abandoned (fail closed → warn)
policy:
  block_severity: high   # findings at this severity or above stop the commit, available options: low / medium / high / critical
reporting:
  show_suggestions: true # include AI fix suggestions in the terminal report

Commit commitgate.yaml so your whole team shares the same gate policy — it contains no secrets.

Usage

commitgate init          # create commitgate.yaml + install pre-commit hook
commitgate scan          # scan staged files (runs automatically via hook)
commitgate install-hook  # install pre-commit hook only (no config file)
commitgate version       # print version
SKIP=all git commit ...  # bypass CommitGate for a single commit

Once the hook is installed, just commit normally. CommitGate intercepts the commit, scans the diff, and either lets it through or blocks it with a report.

Decision outcomes

Manual scan (without committing)

git add <file>
commitgate scan
git restore --staged <file>

How it works

git commit
  └─ .git/hooks/pre-commit  →  commitgate scan
        ├─ gitleaks_runner    scan staged diff for known secret patterns
        ├─ ai_reviewer        LLM semantic review for issues regex can't catch
        ├─ decision_engine    merge findings → allow / warn / block
        ├─ report_generator   Rich terminal output
        ├─ splunk_logger      audit event to Splunk HEC (optional)
        └─ exit code          block → non-zero (stops commit) · allow/warn → 0

Splunk Setup (optional)

CommitGate can send an audit event to Splunk after every scan, giving you a searchable history of every commit decision.

1. Create a Splunk account

Sign up at splunk.com. Start a Splunk Cloud free trial from your account dashboard.

2. Enable HTTP Event Collector (HEC)

In your Splunk UI:

1. Settings → Data Inputs → HTTP Event Collector
2. Click Global Settings → set All Tokens to Enabled → Save

3. Create a HEC token

1. Still on the HTTP Event Collector page → New Token
2. Name: commitgate-audit
3. Click Next → Source type: type commitgate:audit and select New
4. Index: main → Review → Submit
5. Copy the token shown on the confirmation screen

4. Add to your .env

SPLUNK_HEC_TOKEN=your-token-here
SPLUNK_HEC_URL=https://prd-p-yourinstance.splunkcloud.com:8088/services/collector/event
SPLUNK_VERIFY_SSL=false

Why SPLUNK_VERIFY_SSL=false? Splunk Cloud free trial issues certificates missing the Authority Key Identifier extension required by Python 3.10+, making SSL verification impossible on the free plan. Paid Splunk accounts use properly signed certificates and do not need this setting.

5. Verify the connection

Stage any file and run a manual scan:

git add <any-staged-file>
commitgate scan
git restore --staged <any-staged-file>

If the audit event reaches Splunk you'll see no yellow "Splunk audit log failed" warning in the output.

6. View events in Splunk

Search & Reporting → run:

sourcetype="commitgate:audit"

Each commitgate scan appears as one event with action, reason, findings_count, and the full findings list.

Splunk dashboard

Build a CommitGate Security Gate dashboard with these searches:

Module map

See docs/architecture.md for the full architecture and CONTRIBUTING.md for the branch/PR workflow.

Data Privacy

When ai.enabled: true, CommitGate sends your staged code diffs to an external AI provider (whichever you configure in commitgate.yaml). Do not use the AI reviewer on confidential or proprietary code without your organization's authorization. Set ai.enabled: false to run gitleaks only — no data leaves your machine.

Supported providers: Groq, DeepSeek, OpenAI, Gemini. Local LLM support (Ollama) and self-hosted Splunk are on the roadmap so CommitGate can operate fully air-gapped.

License

MIT © 2026 Mike Ly

CommitGate is free to use, modify, and distribute under the terms of the MIT License.