vibe-coded is a simple Rust utility that determines if a repository is
genuine human work or just a simple prompt expansion. It clones a target
repository and runs a set of rules against it to see if it passes the
vibe check.
Grab the latest binary for your system from the Releases page.
If you have Rust installed, you can build it yourself:
cargo install --path .It takes just one argument - the path to the repository you want to check:
vibe-coded https://github.com/exlee/vibe-coded
Repository created at: /var/folders/gg/g9217_cs7t1b1zxqbb21v4fc0000gn/T/vibe-coded/https---github-com-exlee-vibe-7e2bbad21ef1980c
[ VIBE ] repository-age | Age of repository: 0.02 days (< 14 days)
[ VIBE ] repository-dev-time | Development over 0.02 days (< 14 days)
[ HAND ] readme-emoji-count | Emoji count: 0 (>30)
[ HAND ] readme-headings | README.md headings count: 6 (?> 20)
[ HAND ] readme-llm-words | LLM specific words in Readme: 0 (?> 3)
[ HAND ] repository-llm-files | no LLM-tool files
[ FAIL ] code-deletions-average [ FAIL ] code-gap-per-commit [ FAIL ] code-insertions-average [ FAIL ] code-lines-per-hour(failures happen here because this repository is too young to calculate mean with outlier detection)
It is getting harder to figure out if code is someone's crafted work or a simple prompt expansion. This tool runs heuristics to measure the "soul" of the project.
The rules are arbitrary by design.
If you are wondering if a specific rule or check belongs here, the answer is likely "yes." Don't hesitate to make a request or submit a PR. The goal is to define "vibe coded" together, so if you feel it, you can add it (or request).