Alternatives
Products that do what Vibio does
Vibio finds security vulnerabilities in your app/codebase.
- 1
- 2
- 3
- 4EY
I built an open-source AI agent for security testing to find and fix vulnerabilities in your code. I’ve noticed how bad security vulnerabilities have gotten with everyone shipping AI code slop, so I wanted to build something that allows for vibe-coding at full speed without compromising security. Traditional security tools aren’t effective, and manual pen-testing can’t keep up with the rapidly growing AI code This tool runs your code dynamically, finds vulnerabilities, and validates them through actual exploitation. You can either run it against your codebase or enter your (or someone…
2025 · github.com
- 5
Hey HN, I’m Henry, cofounder and CTO at Span (https://span.app/). Today we’re launching AI Code Detector, an AI code detection tool you can try in your browser. The explosion of AI generated code has created some weird problems for engineering orgs. Tools like Cursor and Copilot are used by virtually every org on the planet – but each codegen tool has its own idiosyncratic way of reporting usage. Some don’t report usage at all. Our view is that token spend will start competing with payroll spend as AI becomes more deeply ingrained in how we build software, so understanding how…
Sep 2025 · code-detector.ai
- 6
- 7AI
2025 · github.com
- 8
- 9
- 10VD
Did you know that VSCode extensions run with full access to your system—including file system, network, and credentials? Worse, dozens of malicious extensions have already made it into the marketplace, silently compromising devices. I am a security researcher and student developer who ran into this problem myself. To help tackle this, I built a 100% free tool (no login required) that scans VSCode (and Cursor/Windsurf) extensions for: - Hidden malware and obfuscated code - Dangerous permissions and API misuse - Vulnerable dependencies and suspicious network connections Users have already…
2025 · vscan.dev
- 11
- 12CS
We now write most of our code with agents. For a while, PRs piled up, causing review fatigue, and we had this sinking feeling that standards were slipping. Consistency is tough at this volume. I’m sharing the solution we found, which has become our main product. Continue (https://docs.continue.dev) runs AI checks on every PR. Each check is a source-controlled markdown file in `.continue/checks/` that shows up as a GitHub status check. They run as full agents, not just reading the diff, but able to read/write files, run bash commands, and use a browser. If it finds…
Feb 2026 · docs.continue.dev
- 13
- 14
Find vulnerabilities in your AI prompts before your users do
26d ago · testmyprompt.net
- 15
- 16IB
I built a GitHub app that detects it in pull requests, notifies or blocks them. Alongside it, I published a Semgrep ruleset for any stage of the CI/CD. I started this after getting frustrated by all the FUD around malicious code - lots of noise, little effort to solve it. Having said that, it's still a major attack vector - a stored RCE, with the codebase itself as the sink. Feedback is appreciated. The app, PRevent - https://github.com/apiiro/PRevent The ruleset: https://github.com/apiiro/malicious-code-ruleset The research:…
2025 · github.com
- 17
- 18
- 19
- 20
- 21TO
I'm an infrastructure architect who started using AI assistants to write code 3 months ago. After building several systems with Claude, I noticed a pattern: the code always had security issues I could spot from my ops background, but I couldn't fix them myself since I can't actually write code. Why I built this: I needed a way to verify AI-generated code was production-safe. Existing tools either required cloud uploads (privacy concern) or produced output too large for AI context windows. TheAuditor solves both problems - it runs completely offline and chunks findings into 65KB segments that…
Sep 2025 · github.com
- 22
- 23
- 24
Ranked by how close each launch is in meaning, then by votes. Refine with a description →