Aldasams · HN

Show HN: DocFlow – AI documentation updates for GitHub pull requests

@aryaan_sheth · X

- LLM security for small teams

@dash12_dev · X

analyzes n8n workflows and Make scenarios, finding breakpoints, cost risks, and hidden reliability issues.

@Sakthi_in · X

- Ship AI written code confidently. Catch drift before it compounds.

@fujidevv02 · X

the world's first context-aware, local AI browser pet companion!

thfothijn · Product Hunt

OpzyAI Finds what your AI-built app leaks — your editor fixes it

@MihkelSylla · X

Working on and few other smaller projects for myself

@POONAMSING9999 · X

Forget this fight. The problem in AI is vibe coding security risk so i made vibe Guard ai that analysis user code and found out security risks. For the sake of humanity, to solve a painful problem I made this It had free version try now

@cultkoushik · X

A problem warehouse for creators

@akadhanu · X

an ai sprint retrospectives for it teams (

logphase · HN

I've always struggled to hold a large PR in my head. AI-assisted coding has made it worse. Especially when dozens of files are modified, it became harder to understand what changed: distinguishing important changes from trivial ones and identifying if regressions were introduced. I was also tired of switching between file and method to build the whole picture in my head — I wanted all the context at the point of the function I was reviewing. I guess I'm just more of a visual person. I realized t

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