In short
Vibe X-Ray is the map of your codebase. Every code scan builds it automatically, so you can see what your AI built, where the problems sit and what a change will affect, without reading every file.
What you see
The map has four levels. Start at the top and click down to the detail you need.
- Modules: the main parts of your app, each with its file count, size, findings and a health score.
- Files: every file in a module, with its language, length and findings.
- Functions: the functions, classes and types inside a file, with their line ranges and any findings inside them.
- Connections: what a file imports, what imports it, and how the modules are wired together.
Why it helps with AI-written code
- God files: see that one
api.tsholds fifteen handlers and eight queries. - Tangled modules: spot two parts of the app that import each other.
- Blast radius: before you change or rename something, see every file that depends on it.
- Smaller prompts: give your AI tool only the files connected to the change, instead of half the repository. Fewer tokens, better answers.
Track what changed
Every scan saves a new version of the map. Compare any two versions to see the files and functions that were added, removed or changed, and which findings are new, fixed or still open.
When a function that was clean now has findings, X-Ray marks it as a regression, so you can see which change brought the problem in.
How to use it
- Add a project at app.vibedoctor.io and connect its GitHub repository.
- Run a scan. The map is built automatically after every code scan.
- Open Vibe X-Ray from your project and click through modules, files and functions.
On paid plans, every push to your repository runs a scan and updates the map.
Languages
TypeScript, JavaScript, Python, Go, Java, Rust, C#, Kotlin, Ruby, PHP, Swift, C, C++, Scala, Elixir and Lua.
Use it from your AI app
With the VibeDoctor connector, your AI app can read the map itself through vibedoctor_graph: an overview of the modules, what surrounds a function, what a change affects, test coverage, and a search across functions.
FAQ
Does Vibe X-Ray work with private repositories?
Yes. Connect a public or private GitHub repository to your project and run a code scan. The map is built from that scan.
Is Vibe X-Ray on the free plan?
Yes. Every code scan builds the map, on every plan, including the Free Week.
How often does the map update?
After every code scan. On paid plans, every push to your repository runs a scan, so the map follows your code.
Can I compare any two versions?
Yes. Pick any two scans and X-Ray shows what changed between them.
Does Vibe X-Ray keep my source code?
We scan your code, then delete our copy automatically. The map keeps file and function names, line ranges, how the code connects, findings, and the comments Vibe Story shows.
Want the long version? Read Vibe X-Ray: see what your AI actually built.