Developer Tools1 month ago · 1 tries
Prbl — AI code security scanner
Security scanner that detects vulnerabilities in AI-generated code repositories.
@GetPrbl · X
The full gallery
Tech stack
63 projects
Security scanner that detects vulnerabilities in AI-generated code repositories.
@GetPrbl · X
AI-powered security auditor that scans GitHub repos to find vulnerabilities and suggest fixes.
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
Visualize trends in CVE counts and severity since 2020, broken down by reporting organizations.
u/Secret_Appeal6271 · Reddit
Agents are more capable, and susceptible to exploits, than ever. We're working to stop this from hurting users. AI agents are starting to get real access like GitHub tokens, cloud credentials, customer data, deploy permissions. Not coincidentally, the rate of major cybersecurity incidents is rising rapidly. See for yourself: https://epoch.ai/data/cve?view=graph https://genai.owasp.org/resource/state-of-agentic-ai-security-and-governance/ My friend and I, both AI researchers, are working o
Scan AI prompts and endpoints for vulnerabilities, then monitor LLMs in production for security and compliance.
@CognisafeUK · X
Scans live web apps for security vulnerabilities like exposed keys and open databases in 60 seconds.
@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.
Scan your website for security vulnerabilities and compliance gaps against GDPR and CCPA standards.
@AICybershieldTe · X
Most sites are one scan away from a very bad day. Scanned ~100 this week — exposed .env files, missing security headers, cookies set before consent (a real GDPR fine). Security + privacy + accessibility, one 90s check: #vibecoding #buildinpublic
Upload code to automatically scan for security vulnerabilities.
@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
Scan smart contracts for vulnerabilities and get gas optimization suggestions.
@Ninjafromqueens · X
Hello! I am the founder and owner of Audit your smart contracts before deploying.
Scan any URL for security vulnerabilities: JS CVEs, hidden trackers, and misconfigurations.
@oldagencydev · X
Is this still an open offer?😂I'm launching and trying to get it out there. Free no-signup security scans of any URL to catch everything including vibe-coded app issues. Then paid plans for everything up to enterprise! Already using at my other company!
AI security scanner testing live websites to find vulnerabilities and generate fix prompts.
@wraithnet0x · X
Hey developers! I just launched my agentic security scanner. This is not your basic code review that could be replaced by claude code or anything like that. It tests the live application and hand you the fix so you can secure it in time. Website: Demo⬇️
Analyze code for security vulnerabilities and verify code safety.
@POONAMSING9999 · X
Technology is getting better everyday so the vibe coding but still people loosing money.🚀 Around 62% of vibecode is unsecure. I made VibeGuard that analysis code and check whether it is safe,ready to go,every error and what it can cause, many more...
Scan GitHub repos for security vulnerabilities and code issues, then auto-fix them.
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