@SinghApurv1711 · X

Hey! Check it out here:

@nathanghart · X

Submitting for approval. I built a free tool for anyone about to ship a vibecoded app. It scans your repo for what bites you in prod (leaked keys, no auth, no error handling). I ran it on 1,868 AI-built apps and even caught my own scanner being ~42% wrong.

u/tuco_ye · Reddit

We think GitHub profiles deserve better. So we built GitFlex. We think GitHub profiles deserve better. Every developer has spent hours polishing a CV while their best work is already on GitHub. GitHub tells part of your story. We wanted to help tell the rest. So we built GitFlex - your second CV, powered by real GitHub data. Beta version includes: 🧬 Dev DNA A beautiful, customizable developer portfolio powered by real GitHub data that stays up to date automatically. 🤖 AI R

@aarsh_30 · X

@sacsandc4 · X

@ArthurMrcnr · X

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