@parrotwiki · X

one url. everything they need. code, notes, scripts, keys. end-to-end encrypted. 🦜

@gintentco · X

I know this is a generic ask but could you give it a start on GitHub and share it I need contributors and people to toss ideas around with

@g_saikumar_ · X

Real-time GitHub intelligence for developers, founders, and open-source enthusiasts.

u/uwais_ish · Reddit

Three weeks to build an AI security scanner. The scanner was the easy part. Shipped RedFlag this month. Breakdown of where the time actually went, because it was nothing like I estimated. Stack: Next.js 16, Auth.js v5, MongoDB, Stripe, OpenAI. Deployed on Vercel. What I thought would be hard: getting an LLM to find real vulnerabilities. What was actually hard: getting it to stop finding fake ones. First working version flagged 200+ issues on a clean repo. Every one plausible, most of th

@CodewithDivine · X

check this out

@SinghApurv1711 · X

Hey! Check it out here:

@panditdhamdhere · X

Your GitHub profile, sequenced. Vibe-coded DevDNA for fun Turns any public GitHub user into a fun, shareable Developer Genome report - power level, languages, chaos, coffee estimate, the works. No auth . Just a username. Use it -

u/freestyle_gonzo · Reddit

Vibe coding made building fast. It didn't make understanding easy. Something changed in the last year. Vibe coding (or agentic engineering if you ask some) made writing an app fast. Week-to-weekend fast. More people are building software than ever before, and I think that's a genuinely good thing. But fast building creates a new bottleneck. Writing code is no longer the hard part. Understanding what you built and its nuances is. A huge share of people shipping right now have never analyzed

@nicorask1 · X

Hey Raj, lets connect! I am building a tool that helps saas owners collect feedback from their users and more.

@emanueldev4 · X

Building Preflight a simple way to catch issues before your website goes live.

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

@plaqueboywest · X

I’m building Super Dent X. Connect GitHub once, and it remembers your build journey for you. Curious what you think: Would love your feedback !