@alizreim · X

Documentation that lives in your own git repository

u/Still_Amphibian545 · Reddit

almost launched a side project with my api keys sitting in the repo (a week free gpt 5.6 on us) was about a day from launching a small project when i noticed my openai key was just sitting in a committed file. it had been there for weeks. no idea how i missed it. made me wonder what else was wrong that i couldn't see. turns out for vibecoded stuff it's usually the same handful of things. secrets in the repo, endpoints with no auth, a database with no access rules, no limit on the ex

@david_kubgak · X

Generate a professional README from any GitHub repository in seconds.

dpc94 · HN

Devthropology – Better Insights for GitHub Repos

u/DistinctPicture4660 · Reddit

I built a security scanner that checks every GitHub push and tells AI exactly how to fix the issues Hello, As a developer, I ship a lot of code with Claude Code, and I've used pretty much every security scanner out there. Most of them are great at telling you what's wrong. Then they leave you with a long report, and you're back to copying logs into Claude or Cursor, asking your AI to figure out how to fix everything. I wanted something that fit the way many of us build software today.

u/bob__io · Reddit

What we learned from trying to turn vibe-coded prototypes into production SaaS applications Founder here. While developing MCPBackend, we noticed a major difference between generating a convincing application demo and building a maintainable SaaS product. AI coding tools are increasingly capable of generating interfaces, routes and even initial application logic. But a production application still needs: a reliable data model authentication and authorization backend validation