Vibe check your repo.
How far has your codebase drifted from itself? Paste a public GitHub repo and we run the latest VibeDrift on it — back comes the Vibe Drift Score, a letter grade, and a five-category drift breakdown in seconds. No signup, no install, code never stored.
Public repos only. Runs the latest VibeDrift. Your code is analyzed in memory, never stored.
What a vibe check actually measures
Drift is the gap between the patterns your codebase started with and the patterns new AI-written code keeps introducing — mismatched conventions, duplicated logic, inconsistent error handling, missing auth on a route its neighbors all guard. It compiles. It passes review. It still pulls the codebase out of agreement with itself.
The Vibe Check runs VibeDrift's static analysis over a public repo and scores that coherence 0–100 across five categories: architectural consistency, security posture, redundancy, convention adherence, and scaffolding hygiene. It's the same engine behind the CLI and the in-editor MCP server — this is just the no-install way to point it at any repo and see where it lands.