🛡️ AI Code Guard Pro
Industry-grade security scanner for AI-generated code with AST analysis, taint tracking, and LLM-specific vulnerability detection.
AI coding assistants (GitHub Copilot, Claude, ChatGPT, Cursor) are revolutionizing development—but they can introduce security vulnerabilities that slip past code review. AI Code Guard Pro is a next-generation security scanner specifically designed to catch these issues.
🚀 Key Improvements Over Basic Scanners
| Feature | Basic Scanners | AI Code Guard Pro |
|---|---|---|
| Analysis Method | Regex matching | AST parsing + taint tracking |
| False Positives | High | Reduced via context awareness |
| Secret Detection | Pattern only | Pattern + Shannon entropy |
| Prompt Injection | ❌ Not detected | ✅ Direct + indirect detection |
| Supply Chain | Basic | Typosquatting + dependency confusion |
| Output Formats | Limited | Console, JSON, SARIF, Markdown |
| CI/CD Integration | Basic | Native SARIF for GitHub Security |
🎯 What It Detects
🔐 Secrets & Credentials
- API Keys: OpenAI, Anthropic, AWS, GCP, GitHub, Stripe, and 15+ providers
- Private Keys: RSA, SSH, PGP, EC
- Database Credentials: Connection strings, passwords
- High-Entropy Strings: AI placeholder secrets
💉 Injection Vulnerabilities
- SQL Injection: f-strings, .format(), concatenation in queries
- Command Injection: os.system, subprocess with shell=True
- Code Execution: eval(), exec() with user input
- SSRF: User-controlled URLs in requests
🤖 AI/LLM-Specific Issues
- Direct Prompt Injection: User input in system prompts
- Indirect Injection: RAG/retrieval injection risks
- Unsafe Deserialization: pickle, yaml.load without SafeLoader
📦 Supply Chain Attacks
- Typosquatting: Similar names to popular packages
- Dependency Confusion: Internal package name patterns
- Known Malicious Packages: Database of suspicious packages
📦 Installation
pip install ai-code-guard
Or with development dependencies:
pip install ai-code-guard[dev]
🔧 Quick Start
# Scan a directory
ai-code-guard scan ./src
# Scan with specific output format
ai-code-guard scan ./src --format sarif -o results.sarif
# Quick CI check
ai-code-guard check ./src
# List all rules
ai-code-guard rules
# Create config file
ai-code-guard init
📊 Example Output
🛡️ AI Code Guard Pro v1.0.0
Scanning ./my-project...
┌─────────────────────────────────────────────────────────────────────┐
│ 🔴 CRITICAL: SQL Injection Vulnerability │
├─────────────────────────────────────────────────────────────────────┤
│ 📍 src/db/queries.py:42 │
│ │
│ SQL query constructed using f-string interpolation. User-controlled │
│ data may be interpolated directly into the query, enabling SQL │
│ injection attacks. │
│ │
│ Code: query = f"SELECT * FROM users WHERE id = {user_id}" │
│ │
│ ✅ Fix: Use parameterized queries: │
│ cursor.execute('SELECT * FROM users WHERE id = ?', (user_id,)) │
│ │
│ CWE: CWE-89 │
└─────────────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────────────┐
│ 🟠 HIGH: Prompt Injection Vulnerability │
├─────────────────────────────────────────────────────────────────────┤
│ 📍 src/api/chat.py:23 │
│ │
│ User input directly embedded in LLM prompt via f-string. Attackers │
│ can inject malicious instructions to manipulate the AI's behavior. │
│ │
│ Code: prompt = f"You are a helper. User says: {user_input}" │
│ │
│ ✅ Fix: │
│ 1. Separate system prompts from user content using message roles │
│ 2. Sanitize user input (remove control characters, limit length) │
│ 3. Use structured output formats to detect injection attempts │
│ │
│ CWE: CWE-74 | OWASP: LLM01 │
└─────────────────────────────────────────────────────────────────────┘
────────────────────────────────────────────────────────────────────────
📊 SUMMARY
────────────────────────────────────────────────────────────────────────
Files scanned 47
Issues found 3
Scan time 127ms
🔴 CRITICAL: 1 🟠 HIGH: 2 🟡 MEDIUM: 0 🔵 LOW: 0
────────────────────────────────────────────────────────────────────────
⚙️ Configuration
Create .ai-code-guard.yaml in your project root:
# Minimum severity to report
min_severity: low # critical, high, medium, low, info
# Patterns to ignore
ignore:
- "tests/**"
- "**/test_*.py"
- "examples/**"
- "docs/**"
# Rules to disable
disable_rules: []
# - "SEC001" # If using example API keys
# - "PRI001" # If false positives on prompt construction
# Secret detection tuning
entropy_threshold: 4.5 # Shannon entropy threshold
min_secret_length: 16
# AI-specific detection
detect_placeholder_secrets: true
detect_prompt_injection: true
# Performance
max_file_size_kb: 1024
parallel_workers: 4
🔌 CI/CD Integration
GitHub Actions
name: Security Scan
on: [push, pull_request]
jobs:
security:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: '3.11'
- run: pip install ai-code-guard
- name: Run security scan
run: ai-code-guard scan . --format sarif -o results.sarif --fail-on high
- name: Upload SARIF to GitHub Security
uses: github/codeql-action/upload-sarif@v2
if: always()
with:
sarif_file: results.sarif
Pre-commit Hook
# .pre-commit-config.yaml
repos:
- repo: local
hooks:
- id: ai-code-guard
name: AI Code Guard Security Scan
entry: ai-code-guard check
language: python
types: [python]
pass_filenames: false
GitLab CI
security-scan:
image: python:3.11
script:
- pip install ai-code-guard
- ai-code-guard scan . --format json -o gl-sast-report.json
artifacts:
reports:
sast: gl-sast-report.json
📋 Rule Reference
| Rule ID | Category | Severity | Description |
|---|---|---|---|
| SEC001-015 | Secrets | CRITICAL/HIGH | API keys (OpenAI, AWS, GitHub, Stripe, etc.) |
| SEC020-022 | Secrets | CRITICAL | Private keys (RSA, SSH, PGP) |
| SEC030-031 | Secrets | CRITICAL | Database credentials |
| SEC040 | Secrets | MEDIUM | JWT tokens |
| SEC050 | Secrets | MEDIUM | AI placeholder secrets |
| SEC099 | Secrets | MEDIUM | High-entropy strings |
| INJ001 | Injection | CRITICAL | SQL injection |
| INJ002 | Injection | CRITICAL | Command injection |
| INJ003 | Injection | CRITICAL | Code execution (eval/exec) |
| DES001 | Deserialization | CRITICAL | Unsafe YAML |
| DES002 | Deserialization | CRITICAL | Unsafe pickle |
| SSRF001 | SSRF | HIGH | Server-side request forgery |
| PRI001-005 | Prompt Injection | HIGH | Direct prompt injection |
| PRI006 | Prompt Injection | MEDIUM | User input in prompts |
| PRI010-011 | Prompt Injection | MEDIUM | Indirect injection |
| DEP001 | Dependencies | VARIES | Known suspicious packages |
| DEP002 | Dependencies | HIGH | Typosquatting detection |
| DEP003 | Dependencies | HIGH | Dependency confusion |
🔬 Technical Details
AST-Based Analysis
Unlike regex-based scanners, AI Code Guard Pro parses Python code into an Abstract Syntax Tree, enabling:
- Taint tracking: Follow user input through variable assignments
- Context awareness: Understand function calls and their arguments
- Reduced false positives: Skip patterns in comments and strings
Entropy-Based Secret Detection
Uses Shannon entropy to distinguish real secrets from placeholders:
# High entropy (likely real secret) - DETECTED
api_key = "sk-proj-aB3xK9mL2pQrStUvWxYz..."
# Low entropy (placeholder) - IGNORED
api_key = "your-api-key-here"
LLM Security Focus
Specifically targets vulnerabilities in AI/LLM applications:
- Detects prompt injection in OpenAI, Anthropic, and LangChain code
- Identifies indirect injection risks in RAG pipelines
- Flags unsafe patterns in agent/tool implementations
🤝 Contributing
Contributions welcome! See CONTRIBUTING.md for guidelines.
Adding Detection Patterns
# ai_code_guard_pro/analyzers/my_analyzer.py
from ai_code_guard_pro.models import Finding, Severity, Category
class MyAnalyzer:
def analyze(self) -> list[Finding]:
findings = []
# Your detection logic
return findings
📚 References
📄 License
MIT License - see LICENSE for details.
Built for the AI era by security engineers who use AI coding assistants daily 🛡️
Metadata
Release files for ai-code-guard 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ai_code_guard-1.0.0.tar.gz | 31.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ai_code_guard-1.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.8 kB
Release files / ai_code_guard-1.0.0.tar.gz
| Download URL | ai_code_guard-1.0.0.tar.gz |
|---|---|
| Size | 31.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fea2508e3ff8eb7a3eacdd313725cf6067f5f532b115db415832807732e36b38
|
|
BLAKE2b-256 checksum How to use checksums |
bd8e9858030de3753730918c0ffaba018485cd2891765cf0d909057e275b47fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / ai_code_guard-1.0.0-py3-none-any.whl
| Download URL | ai_code_guard-1.0.0-py3-none-any.whl |
|---|---|
| Size | 35.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4fc1175bec933667d773d3c15f65510945bc21ca5c39e024fa1fab9895186780
|
|
BLAKE2b-256 checksum How to use checksums |
34ce7d15f212f5a37d3b4c1633731409cf8b0aa3740f93d1a604f44b9a1948eb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for ai-code-guard 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.