I used Claude Code heavily while trying to launch an app while being quite sick and my mental focus was not at its best. So I relied 'too much' on Claude Code, and my Supabase keys slipped in a 'hidden' endpoint, causing some emails to be leaked.

After some deep introspection, and thinking about the explosion of Lovable, Replit, Cursor, Claude Code vibe-coded apps, I thought about what's the newest newest and most dreadful pain points in the dev arena right now. And I came up with the scenario of debugging some non-obvious errors, where your AI of choice will reply "You're absolutely right! Let me fix that", but never nailing what's wrong in the codebase.

So I built Ubon for the last week, listing thoroughly all the pain points I have experienced myself as a software engineer (mostly front-end) for 15 years. Ubon catches the stuff that slips past linters - hardcoded API keys, broken links, missing alt attributes, insecure cookies. The kind of issues that only blow up in production.

And now I can use Ubon by adding it to my codebase ("npx ubon scan .", or simply telling Claude Code "install Ubon before commiting"), and it will give outputs that either a developer or an AI agent can read to pinpoint real issues, pinpointing the line and suggested fix.

It's open-source, free to use, MIT licensed, and I won't abandon it after 7 days, haha. My hope is that it can become part of the workflow for AI agents or as a complement to linters like ESlint.

It makes me happy to share that after some deep testing, it works pretty well. I have tried with dozens of buggy codebases, and also simulated faulty repos generated by Cursor, Windsurf, Lovable, etc. to use Ubon on top of them, and the results are very good.

Would love feedback on what other checks would be useful. And if there's enough demand, I am happy to give online demos to get traction of users to enjoy Ubon.