VibeFix
Detects AI-generated code in GitHub pull requests and assigns a maintainability score.
not read yet
Use
- For
- Engineering teams reviewing pull requests for AI-generated code in GitHub repositories
- Price
- From $9/mopricing page, read 2026-09-20
- Activity
- Maintainednothing dated on the site
- Company
- founding year not on record
- Scan pull requests for AI-generated code patterns and assign quality scores
- Block merges exceeding configured AI signature thresholds before deployment
- Compare multiple pull requests side-by-side with quality recommendations
- #115
CodeRabbit
Automatically reviews pull requests, prioritizes them by risk, and scans for security vulnerabilities.
24.4knot readFrom $24/user/mo2023 - #148
Hexmos
AI code reviewer that flags logic errors, credential leaks and bugs at commit time before reaching production.
26.2kMaintained— - #195
Greptile
Reviews pull requests and tests code changes using agent swarms to catch bugs and style violations across codebases.
8.5knot readFrom $30/user/mo - #206
Fluid Attacks
Scans applications for vulnerabilities using automated analysis and human penetration testing, prioritizes findings by exploitability, and generates remediation guidance.
4.3knot readFree plan - #219
Hacktron AI
Analyzes pull requests to find exploitable vulnerabilities and generates working proofs of concept before code ships.
68not readFrom $40/user/mo - #278
KushoAI
Generates API tests from specifications, scans for security vulnerabilities, and validates complete workflows across services.
906not readFree plan
What is VibeFix?
Detects AI-generated code in GitHub pull requests and assigns a maintainability score.
Who is VibeFix for?
Engineering teams reviewing pull requests for AI-generated code in GitHub repositories
How much does VibeFix cost?
Paid plans start at $9/mo, per VibeFix's pricing page on 2026-09-20.
Do people use VibeFix?
Emerging.
Is VibeFix still maintained?
Maintained.
What are alternatives to VibeFix?
In Developer tools, by use: CodeRabbit, Hexmos, Greptile, Fluid Attacks, Hacktron AI, KushoAI.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one row at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.