VibeSec 🛡️
Stop drowning in false positives. Catch real vulnerabilities, silence security noise with local on-device AI, and auto-fix your code.
Most static analysis tools flood developers with hundreds of alerts for test mocks, dead branches, and benign string templates.
VibeSec combines static analysis, secret detection, and dependency audits with a tiny on-device AI model that runs in ~15ms on pure CPU. It automatically filters out false positives—100% locally with zero cloud telemetry.
⚡ Quickstart
Install via pip:
pip install cybereiche-vibesec
Run a scan in your project folder:
vibesec scan .
What You See in the Terminal
Scanning project at /my-app...
✓ Secrets: 0 leaks detected
✓ SAST: 1 confirmed risk (2 false positives suppressed by local AI)
✓ SCA: 1 CVE detected in requirements.txt
[CRITICAL] SQL Injection in app/db.py:42
Code: cursor.execute(f"SELECT * FROM users WHERE id = {user_id}")
AI Confidence: 98% (Confirmed Injection Vector)
Fix: vibesec fix . --apply
[SUPPRESSED] 2 False Positives Filtered
• tests/mock_auth.py:12 — Hardcoded test credential (mock harness)
• utils/logging.py:88 — Benign string formatting (sanitized input)
Run 'vibesec scan . --show-suppressed' to inspect filtered alerts.
💡 Why VibeSec?
- Local AI Noise Reduction: A compiled 22 MB on-device transformer model filters out 40–60% of bogus SAST alerts in ~15ms on standard CPU. Zero code ever leaves your laptop or CI runner.
- All-in-One Scanning:
- Secrets: API keys, tokens, and credentials (Gitleaks & detect-secrets).
- SAST: Vulnerabilities like SQL injection, command execution, and path traversal.
- Polyglot SCA: Dependency CVE audits via Google OSV across Python, JS/TS, Go, Rust, Java, and Ruby.
- AI & LLM Risks: AST checks for prompt injection and unsafe agent shell execution.
- Verified Code Fixes: Don't just find vulnerabilities—fix them. VibeSec proposes syntax-checked diffs and verifies them against your local test suite (
pytest,npm test) before applying changes. - Zero-Config CI/CD: Native PR annotations (
::error::), step summaries, and OASIS SARIF v2.1.0 output for GitHub Security and GitLab Security Dashboards without third-party bot tokens.
🛠️ CLI Usage Guide
1. Basic Scan (Default with AI Noise Reduction)
Scans your repository, runs all engines in parallel, and applies on-device noise reduction:
vibesec scan .
2. Inspect Filtered Alerts
Want to see what the AI suppressed and why?
vibesec scan . --show-suppressed
3. Strict Review Mode
Flags all borderline alerts for human review:
vibesec scan . --strict
4. Raw Scanner Mode (Disable AI Filtering)
Bypasses the triage model to inspect unfiltered scanner output:
vibesec scan . --no-triage
5. Export SARIF Report for CI/CD
Generates schema-compliant SARIF v2.1.0 for the GitHub Security tab:
vibesec scan . --sarif vibesec-results.sarif --severity HIGH
6. Auto-Fix Vulnerabilities
Preview or apply automated code patches:
# Preview proposed fixes (dry-run)
vibesec fix . --dry-run
# Apply verified fixes only if your test suite passes
vibesec fix . --apply --run-tests
🤖 Auto-Remediation Setup (Optional)
VibeSec can synthesize localized security patches using your preferred LLM provider via LiteLLM (Claude, GPT-4o, DeepSeek, or local Ollama/vLLM):
# Configure API keys via environment or .env:
export ANTHROPIC_API_KEY="sk-ant-..."
# or for local private models:
export VIBESEC_LLM_MODEL="ollama/llama3"
export VIBESEC_LLM_API_BASE="http://localhost:11434/v1"
Or configure via .vibesec.yaml:
remediation:
enabled: true
model: "claude-3-5-sonnet-20241022" # or gpt-4o, ollama/llama3
⚙️ Configuration (.vibesec.yaml)
Customize rules and thresholds with an optional .vibesec.yaml file:
version: 1
settings:
severity_threshold: "HIGH" # LOW | MEDIUM | HIGH | CRITICAL
fail_on_findings: true
triage:
enabled: true
threshold_confirm: 0.65
threshold_suppress: 0.15
zero_drop_critical: true
scanners:
sast:
enabled: true
secrets:
enabled: true
sca:
enabled: true
ignore:
paths:
- "tests/**"
- "docs/**"
- "node_modules/**"
🛡️ GitHub Actions Workflow
Add VibeSec to .github/workflows/security.yml for automated PR checks:
name: Security Audit
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
audit:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: "3.11"
- run: pip install cybereiche-vibesec
- run: vibesec scan . --severity HIGH --sarif vibesec-results.sarif
- uses: github/codeql-action/upload-sarif@v3
if: always()
with:
sarif_file: vibesec-results.sarif
🔒 Privacy, Air-Gap & Enterprise Compliance
For teams with strict data sovereignty and regulatory requirements:
- Strict Air-Gap & Zero Telemetry: Scans and machine-learning triage execute 100% locally in ephemeral process memory. Zero source code, snippets, or metadata ever leave your machine.
- Zero-Drop Critical Policy: High-severity risks (CVSS 9.0+) and Remote Code Execution patterns are hardcoded to never be auto-suppressed.
- EU & DACH Compliance: Built to adhere to GDPR Article 25 (Privacy by Design), EU AI Act transparency rules, and BSI IT-Grundschutz standards.
- For formal architecture specifications, threat modeling, and regulatory mappings, see DACH_EU_COMPLIANCE_AND_THREAT_MODEL.md.
📄 License
VibeSec is distributed under the Apache 2.0 License.
Developed and maintained by CyberEiche.
Metadata
Release files for cybereiche-vibesec 0.2.2
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 | Actions |
|---|---|---|---|---|
| cybereiche_vibesec-0.2.2.tar.gz | 18.7 MB | Without provenance | Details for cybereiche_vibesec-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cybereiche_vibesec-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for cybereiche_vibesec-0.2.2-py3-none-any.whl |
Total release size: 37.4 MB
Release files / cybereiche_vibesec-0.2.2.tar.gz
| Download URL | cybereiche_vibesec-0.2.2.tar.gz |
|---|---|
| Size | 18.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
899e6a99361b5c368712a0732fbc0083d25a155907092e39106d79d9b4614bac
|
|
BLAKE2b-256 checksum How to use checksums |
dbebb5b6e63b43d13879a5b3d9aab700e0a744680fe0ffd8a745b5609c649513
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Release files / cybereiche_vibesec-0.2.2-py3-none-any.whl
| Download URL | cybereiche_vibesec-0.2.2-py3-none-any.whl |
|---|---|
| Size | 18.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7ecd68b64321c482f79914527cea5d5d412c9f02e2115f75b9588977e89970f0
|
|
BLAKE2b-256 checksum How to use checksums |
4d4760d147256c0542b8014aaab1c0fd2b1256b56449ea50f769a7b4f124f072
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.15
|
Security for cybereiche-vibesec 0.2.2
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.