PRIVATE BETA

Vibe Check.

Production-readiness feedback for AI coding agents.

Vibe Check is a technical-debt guardrail for JavaScript and TypeScript codebases where AI agents write most of the code. It scans changed files in under two seconds, blocks agents on critical findings, and ratchets debt so it only goes down.

Detection and scoring

Seventeen detection plugins cover debt that piles up quietly: TODO markers, lint suppressions, type-safety escapes, duplication, and empty catch blocks. Every scan also produces a 0 to 100 Vibe Score, publishable as a README badge with no server behind it. Automated fixes handle the mechanical cases, like turning a ts-ignore into a ts-expect-error.

Setup and scans

One init command scaffolds config plus hooks for Claude Code, Cursor, or pre-commit; nothing to host. Incremental scans cover only changed, staged, or branch files and finish in under two seconds. Exit codes do the talking: 0 passes, 1 warns, 2 blocks, and Claude Code treats a block as a stop.

Ratchet gates

Ratchet gates give every rule a cap equal to today's count, so CI fails the moment a count rises. Reductions lock in as the new cap, with an audit history you commit to git. The gate fails closed: a broken config or missing plugin never reports a pass.

Who it is for

Vibe Check is for engineering teams whose JavaScript or TypeScript code is largely written by AI agents, and the agents themselves.

Where it stands

Vibe Check is working software, published privately to GitHub Packages and already gating Neua's own repositories. The beta is closed; getting in means a read token for the package registry, issued by request.

Join the beta

The team reads every request and replies by email with registry access and setup steps.