Blog

Security guides for
vibe-coded apps.

Practical, no-jargon guides to help you find and fix the vulnerabilities AI leaves behind.

scan my app for exposed secrets

Scan my app for exposed secrets with practical checks

A practical guide to finding leaked API keys, tokens, and private credentials in source files, Git history, client bundles, and logs before launch.

5 min read
is claude code safe

Is Claude Code safe after the leak? What users should do

A practical post-incident guide to Claude Code safety: what changed after the leak, what to verify in the npm package, and what users should do now.

6 min read
claude code leak

Claude Code leak: what happened and what it means

A clear breakdown of the Claude Code leak, the exposed npm build, what was actually disclosed, and why the March 31, 2026 incident matters to developers.

6 min read
vibe coded app security check

Vibe coded app security check for prelaunch review

A practical prelaunch security review for AI-built apps. Use this checklist to catch secret leaks, weak auth, unsafe endpoints, and risky defaults before launch.

6 min read
ai app security audit

AI app security audit: what to check before launch

A practical security review for AI-built apps before launch. Check auth, secrets, data access, unsafe actions, logs, headers, and dependency risk.

6 min read
common security mistakes in ai generated apps

Common security mistakes in AI generated apps to fix

The biggest security failures in AI-built apps are usually simple: leaked secrets, broken auth, unsafe file handling, and skipped review before launch.

7 min read