| Source | Publisher | Used for |
|---|---|---|
| Secure Vibe Coding: Essential Security Guidance for Non-Technical Users | Cloud Security Alliance | Sections 01, 02 (secrets management, vulnerability classes, AI/human review checklist) |
| Vibe Coding Security Risks Aren't Like Ordinary Security Risks | IBM Think | Sections 00, 02 (exposed secrets rate, missing auth, slopsquatting, supply-chain risks) |
| AI coding assistants twice as likely to leak secrets, as overall leaks rise 34% | SC World (SC Media) | Section 00 (secret-leak statistic corroboration) |
| The State of Secrets Sprawl 2026 | GitGuardian | Section 00 (secret-leak statistic corroboration) |
| OpenAI Spend Limit: How to Cap Your API Bill (2026) | Alephant | Section 03 (spend limits as notifications, layered cost-control tactics) |
| When to Stop Vibe Coding and Hire a Developer Instead | Vibe Coder Blog | Section 05 (concrete warning signs to hire an engineer) |
| What broke first when you tried to scale a vibe-coded project? | Product Hunt (Vibecoding Discussion Forums) | Section 04 (what breaks first at scale) |
| Synthetic Monitoring for Vibe Coded Apps: Why You Need It | dotcom-monitor | Section 04 (uptime/monitoring guidance) |