
StackMind — Second Brain for Developers
为开发者设计的笔记应用,支持代码块、看板管理和GitHub导入。
@SinghApurv1711 · X
Hey! Check it out here:
完整作品展
技术栈
23 projects

为开发者设计的笔记应用,支持代码块、看板管理和GitHub导入。
@SinghApurv1711 · X
Hey! Check it out here:

用对抗测试检查LLM端点安全,获取OWASP审计报告。
@aryaan_sheth · X
- LLM security for small teams

Plaintext 检查 AI 生成应用中的安全漏洞(代码、端点和数据库)。
@plaintextsecure · X
Security Scanner for Vibe Coded apps to prevent data and money leaks

用多个模型实时审计AI回应以判断其可靠性。
u/inc_23 · Reddit
Hey, I created a tool that catches when your LLM is confidently wrong, in production, in real time — looking for beta testers. Your bot sounds sure of itself even when it's wrong, and you usually only find out when a customer complains. Auscope audits every LLM response in the background: 3 models from 3 different providers independently check it, a 4th "chairman" model resolves disagreements, and you get one verdict — verified, uncertain, or unreliable. Runs async, doesn't slow your respon

Stepflo 连接 GitHub 代码库,自动检测用户流并生成可视化地图。
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

由AI驱动的代码审查工具,在microVM中运行代码来捕获更多错误。
u/dumbfoundded · Reddit
Ito, AI Code Review that Runs Code I've been using AI code review tools but none of them actually run code so I built one: https://www.ito.ai/ The way it works is that it uses microVMs to spin up your environment with all of the services running. Then a bunch of AI agents go and test the application to collect runtime evidence. The result is you get test cases along with evidence about whether or not the test cases pass or fail. The runtime evidence can be videos, request/response curls, db

ShipSecurely — AI应用安全审计清单,包含可复制的编码代理提示。
@zeeshan4015 · X
You vibe coded it. Now secure it. 🛡️ ShipSecurely — a free security checklist with 1-click audit prompts for Coding agents. Find and fix security vulnerabilities: Just copy paste the prompts to your coding agent and fix critical ones before launching

扫描网站检测 vibe-coding 模式和安全头部。
u/RockettBits · Reddit
I built a tool that tells you why a website “looks vibe coded” and how to improve it. Some of us use vibe coding because it’s insanely fast, and honestly, a lot of the results are pretty good. But there’s also this weird thing where you open a website and can almost instantly tell it was vibe coded. Same cards, same rounded corners, same gradients, same spacing, same component-library feel. People usually just call it “AI slop,” but I wanted to understand what actually creates that feeling.

检查 RAG 块并可视化 AI 代理工作流、内存架构和执行轨迹。
@Higgs0110 · X

VibeLint 为 AI 代理提供代码检查、权限控制和审批工作流。
@RElharrak39428 · X

审计AI应用的安全漏洞,获取完整检测报告。
u/mrtrly · Reddit
I asked ChatGPT 20 different ways who could fix a half-built app. It never named my company once. I do codebase rescue for founders in exactly that spot, so that one stung. There are already plenty of tools that measure this kind of AI visibility, a CDN even ships one free, so I built mine mostly to see my own number, and it confirmed the bad news: near zero. The measuring turned out to be the easy part. What none of the tools do, and what I actually care about, is the fix: getting the mode