开发者工具3 weeks ago
attestd | CVE API for Machine-Readable Vulnerability Risk Signals
将CVE漏洞数据转换为机器可读风险信号的API，用于自动化。
robert_marshall5 · Product Hunt
attestd CVE and supply chain risk signals for autonomous AI agents.
完整作品展
技术栈
23 projects
将CVE漏洞数据转换为机器可读风险信号的API，用于自动化。
robert_marshall5 · Product Hunt
attestd CVE and supply chain risk signals for autonomous AI agents.
Vulnsy是为安全团队提供的渗透测试报告平台，可10倍快速交付客户报告。
@TurvSec · X
AI 应用安全扫描器，检测泄露的密钥和配置问题。
thfothijn · Product Hunt
OpzyAI Finds what your AI-built app leaks — your editor fixes it
扫描你的应用中泄露的API密钥、开放数据库和身份验证绕过。
@Nqspq · X
been building a security scanner for vibe-coded apps — it catches leaked API keys, open databases, logins you can bypass. tested it on a repo made for testing scanners. it caught everything — report below free if you want to check yours:
VibeLint 为 AI 代理提供代码检查、权限控制和审批工作流。
@RElharrak39428 · X
为团队和应用安全管理密钥与环境变量。
@radimhfer · X
i'm founder of Stashbase, designed to help builders
Tako 在 60 秒内扫描网页应用，发现泄露密钥和开放数据库等安全漏洞。
@guhanvenkaty · X
Tako's free preview is live: Paste your URL, get a security verdict on your vibe-coded app in 60s. Not an AI wrapper: it fires real requests and PROVES exposure, pulling data from your open DB with no login. Scanning puts you on the early-access waitlist.
粘贴 GitHub 仓库扫描安全漏洞，自动修复代码问题。
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
为GitHub仓库运行安全审计，检测密钥泄露、认证问题和部署漏洞。
@emanueldev4 · X
Building Preflight a simple way to catch issues before your website goes live.
扫描GitHub代码库查找安全漏洞，AI提供修复建议。
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
扫描 GitHub 仓库检查生产就绪度、安全性和可扩展性。
@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.
