This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
SecureVibe
Security scanner that finds and fixes code vulnerabilities
SecureVibe is security scanner that finds the vulnerabilities that actually matter. It reconciles regex, AST and a knowledge graph, then ranks each finding by whether a public route can actually reach it — so you triage real exploit paths, not noise. Optional AI fixes (bring your own key), plain-language Ask the Graph queries, CWE/category filters, and an A-F risk grade. On the OpenSSF CVE benchmark: adjusted F1 81.7, #2, ahead of Codex and Claude Code.
I've been working on a project called SecureVibe over the past few months.
The idea came from something I've been noticing: we're shipping software faster than ever, but security doesn't always keep up with development.
So I started building SecureVibe, a code security scanner that aims to help developers find vulnerabilities and understand whether they're actually exploitable.
It's currently an MVP, and there's still a lot of work to do, but I wanted to share it and get some feedback from other developers and security engineers.
Here's what it currently does:
1. Vulnerability Detection: Scans your codebase and shows detected vulnerabilities with relevant code snippets and locations.
2. AI-Powered Fixes: An optional AI fixing feature. For now, you can use your own API key.
3. Ask the Graph: You can ask questions about your codebase, such as where an attacker could potentially exploit your application or whether there are authentication-related security issues.
4. Filtering & Reports: Filter vulnerabilities by categories such as CWE, database injection, and more. You can also download an interactive HTML report to review findings and work on fixing them later.
5. Attack Path Analysis: This is one of the parts I've spent quite some time on. Rather than simply scanning code and reporting issues, SecureVibe uses Tree-sitter and AST analysis to understand code context and build a graph connecting application routes, handlers, and database calls. This helps determine whether findings are actually reachable and classify them as Confirmed or Likely.
Some validation I've done:
One of the challenges I faced was finding reliable benchmarks to validate the security rules and measure detection accuracy.
After some research, I started using the OpenSSF CVE benchmark. SecureVibe achieved a raw F1 score of 77.5 and an adjusted F1 score of 81.7.
However, I'm still working on reducing false positives and improving detection accuracy. There's definitely room for improvement.
What I'd really appreciate help with:
- If you try it, did you encounter any false positives or missed vulnerabilities?
- Did you run into any issues while scanning your repository?
- Were the findings and attack paths actually useful?
- Is there anything you'd expect from a tool like this that is currently missing?
It's still an MVP, and I'm looking for honest feedback to help decide what to improve in the next development phases.
The scanner currently works best with TypeScript repositories, so I'd recommend starting there.
I'd genuinely appreciate anyone willing to give it a try.
Thanks!
About SecureVibe on Product Hunt
“Security scanner that finds and fixes code vulnerabilities”
SecureVibe was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #458 on the daily leaderboard. SecureVibe is security scanner that finds the vulnerabilities that actually matter. It reconciles regex, AST and a knowledge graph, then ranks each finding by whether a public route can actually reach it — so you triage real exploit paths, not noise. Optional AI fixes (bring your own key), plain-language Ask the Graph queries, CWE/category filters, and an A-F risk grade. On the OpenSSF CVE benchmark: adjusted F1 81.7, #2, ahead of Codex and Claude Code.
On the analytics side, SecureVibe competes within Developer Tools, Security and Vibe coding — topics that collectively have 527.1k followers on Product Hunt. The dashboard above tracks how SecureVibe performed against the three products that launched closest to it on the same day.
Who hunted SecureVibe?
SecureVibe was hunted by Abdo Mohamad. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of SecureVibe including community comment highlights and product details, visit the product overview.
Hey everyone!
I've been working on a project called SecureVibe over the past few months.
The idea came from something I've been noticing: we're shipping software faster than ever, but security doesn't always keep up with development.
So I started building SecureVibe, a code security scanner that aims to help developers find vulnerabilities and understand whether they're actually exploitable.
It's currently an MVP, and there's still a lot of work to do, but I wanted to share it and get some feedback from other developers and security engineers.
Here's what it currently does:
1. Vulnerability Detection: Scans your codebase and shows detected vulnerabilities with relevant code snippets and locations.
2. AI-Powered Fixes: An optional AI fixing feature. For now, you can use your own API key.
3. Ask the Graph: You can ask questions about your codebase, such as where an attacker could potentially exploit your application or whether there are authentication-related security issues.
4. Filtering & Reports: Filter vulnerabilities by categories such as CWE, database injection, and more. You can also download an interactive HTML report to review findings and work on fixing them later.
5. Attack Path Analysis: This is one of the parts I've spent quite some time on. Rather than simply scanning code and reporting issues, SecureVibe uses Tree-sitter and AST analysis to understand code context and build a graph connecting application routes, handlers, and database calls. This helps determine whether findings are actually reachable and classify them as Confirmed or Likely.
Some validation I've done:
One of the challenges I faced was finding reliable benchmarks to validate the security rules and measure detection accuracy.
After some research, I started using the OpenSSF CVE benchmark. SecureVibe achieved a raw F1 score of 77.5 and an adjusted F1 score of 81.7.
However, I'm still working on reducing false positives and improving detection accuracy. There's definitely room for improvement.
What I'd really appreciate help with:
- If you try it, did you encounter any false positives or missed vulnerabilities?
- Did you run into any issues while scanning your repository?
- Were the findings and attack paths actually useful?
- Is there anything you'd expect from a tool like this that is currently missing?
It's still an MVP, and I'm looking for honest feedback to help decide what to improve in the next development phases.
The scanner currently works best with TypeScript repositories, so I'd recommend starting there.
You can try it here:
https://securevibe-dev.vercel.app/
I'd genuinely appreciate anyone willing to give it a try.
Thanks!