L'accroche
AI-generated code can move faster than the review habits around it. The failure mode is rarely one dramatic prompt; it is a repo with no automated security checks, no dependency update loop, no secret scanner, and no instruction file telling agents to preserve auth, RLS, CORS, CSP, and test coverage.
Comment ça marche
The repo check looks for web-app signals, then audits CI workflows, dependency automation config, secret-scanner config, and AI-agent instruction files such as AGENTS.md, CLAUDE.md, Copilot instructions, or Cursor rules. Missing guardrails become one consolidated finding rather than four noisy findings.
Le rayon d'impact
Without guardrails, AI-assisted edits can introduce raw SQL interpolation, unsafe HTML sinks, leaked keys, decode-only JWT handling, permissive CORS, or removed authorization checks without any automated system stopping the merge.
// what fixvibe checks
What FixVibe checks
FixVibe repo scans look for high-confidence security patterns and dependency risk in source context. Reports identify the affected area and recommended fix. For check-specific questions about exact detection heuristics, active payload details, or source-code rule patterns, contact support@fixvibe.app.
Défenses blindées
Add CodeQL or Semgrep, Gitleaks or TruffleHog, Dependabot or Renovate, and normal test/typecheck gates to CI. Update AI-agent instructions to require auth/RLS review, secret handling, OWASP-style checks, no weakening of security controls, and regression tests for security-sensitive changes.