Back to browse
GitHub Repository

CLI utility to check if Git repo was vibe-coded or not

2 starsRust

Vibe-coded – Rust CLI to discover LLM-assisted Git repositories

by xlii·Feb 12, 2026·1 point·0 comments

AI Analysis

●●SolidNiche GemShip It
The Take

Handy CLI that actually pulls a repo and runs a battery of concrete heuristics — repo age, README keywords/emoji counts, commit velocity, presence of LLM-tool files, and simple commit-statistics — to guess whether code was prompt-expanded. The rule set is intentionally arbitrary and extensible, which makes this a useful starting point for audits or CI checks, but expect false positives and plan to tune or add rules for your context.

Target Audience

Developers, repository maintainers, code reviewers and security researchers who want to flag likely LLM-generated projects

Post Description

A simple CLI to check repository for parameters and decide whether it (seems) to be vibe or hand coded. See example on GitHub page.

Rules are pretty arbitrary and (with Rust) can be easily added for more checks in case anyone wants to contribute :)

Similar Projects

AI/ML●●Solid

Letta – Git-Based Memory for Coding Agents

Context Repositories — treating agent memory like a git repo you can diff, branch, and version — is a clever, developer-friendly twist on long-term LLM state. Letta Code’s persisted, model‑agnostic agents and the Conversations API make the product feel like a coherent stack for production agents, though the trick will be real-world scale, merge semantics, and cost of storing rich context over time.

Big BrainBold BetSlick
morawr
204mo ago

Vibe Code your 3D Models

OpenSCAD IDE with AI refactor, but parser is immature and audience is niche.

Ship ItWizardry
burrnii
61203mo ago