How organizations can secure their AI-generated code
The IT manager didn’t know the company hired a “vibe coder” straight out of school. By the time they met a few months later, the new hire had already built a web application that operated with customer data and private contracts. The app ran under a domain the new hire controlled, stored data on Supabase’s free plan, and deployed directly from his GitHub repository to Cloudflare’s serverless infrastructure. “He vibe-codes everything straight into production, on servers all over the world,” the IT manager wrote on Reddit . “We’re EU based.” When asked whether he had read the AI-generated code or taken any security precautions, the new hire said, “My GitHub repo is private.” The IT manager took the concern to the CEO, who brushed it aside: “Let it go.” In many organizations, vibe coders build software without thinking much about security. Their apps may get the job done, but they are ticking bombs. In SusVibes , a benchmark of 186 real-world feature requests from open-source projects, ag