ESLint enforces code style. VibeCode QA measures code health.
They're complementary, not competing. vcqa actually runs your ESLint as part of its Lint check. But vcqa goes far beyond linting:
| VibeCode QA | ESLint | |
|---|---|---|
| Purpose | Holistic code health scoring | Code style + bug pattern linting |
| Scope | 34 checks: security, testing, architecture, AI readiness, env, containers, memory | Lint rules only |
| Config | Zero config | eslint.config.js required |
| Linting | Delegates to your ESLint/Biome (auto-detected) | Native (500+ rules) |
| Security | 31 CWE patterns + secret detection + npm audit | Only with eslint-plugin-security |
| Testing | Pyramid, coverage, execution, quality metrics | No |
| Architecture | Import graph, circular deps, god modules, SVG diagrams | No (eslint-plugin-import for basic cycle detection) |
| Complexity | Cognitive complexity per function | Only with complexity rule |
| Duplication | Copy-paste detection | No |
| Type checking | Runs tsc --noEmit | Only with typescript-eslint type-aware rules |
| AI readiness | Confusion index + context locality | No |
| AI-powered fix | Claude-powered fixes | --fix (pattern-based only) |
| Score | Weighted composite 0-100 with grade | No score (pass/fail per file) |
| Report | HTML dashboard with charts + diagrams | Text/JSON output |
| Trends | Score timeline over 30 runs | No |
The best setup is ESLint (or Biome) for real-time lint feedback in your editor, plus VibeCode QA for the bigger picture — security, architecture, testing, and AI readiness. vcqa automatically uses your ESLint config, so you get lint results as part of the health score without duplicating work.
npx @vibecodeqa/cli # runs your ESLint + 28 more checks