Containarium

nd OpenAI Codex). This workflow—often called "vibe coding"—involved describing the desired functionality and letting the AI assemble the codebase. The project worked perfectly, but the AI pinned a vulnerable dependency version in the package.json. Because the app ran normally and passed functional tests, we missed the audit step. Automated scanners found the vulnerability within hours. THE BROADER LESSON AI increases development speed, but it also increases the "security debt" of every deployment. In traditional development, you review versions carefully. With AI-generated scaffolding, that step is easy to overlook. The attack chain: AI-generated project -> Vulnerable dependency -> Middleware bypass -> Automated scan -> Cryptominer HOW WE FIXED IT We realized that if we are using AI to speed up development, we need automated "brakes" to match that speed. We moved our apps onto Containarium ( https://github.com/FootprintAI/Containarium ), an open-source platform that uses ZFS-backed, unprivileged LXC containers to consolidate 100+ isolated environments onto a single VM with integrated security monitoring and vulnerability scanning. This ensures that even if a developer accidentally deploys a vulnerable dependency, the breach is isolated from the host and flagged by runtime monitoring. OPEN QUESTION I’m curious how others are handling the "AI audit" problem. Are you adding automated security gates to your dev environments, or are you strictly relying on traditional dependency scanning and hoping the "vibe" doesn't miss anything?

- Security concerns we might be underestimating - Where this approach breaks down in real-world usage - Alternatives we should be considering (LXD, Proxmox, something else?) Tradeoffs we’re aware of: - Shared kernel (not VM-level isolation) - Not suitable for untrusted workloads - Linux-only - Requires infra discipline (limits, monitoring, backups) This is early-stage and open source. APIs and workflows will evolve. We’re not trying to “replace Kubernetes” — just trying to do one thing well: cheap, fast, SSH-based dev environments. Would love blunt feedback from folks who’ve been down this road before.