Check the health of a project's code
Codebase Stats sizes up a project folder: its files, code health, git history, packages, test coverage and what its sessions cost.
Codebase Stats looks through a project's folder and shows how big it is, how healthy the code looks, how active it is in git, which packages it depends on, how well it is tested and what its sessions have cost. It reads your files on this computer and does not use AI.
Open Codebase Stats#
In the sidebar, open the menu on a project.
Click View Codebase Stats.
Pick a tab: Overview, Files, Health, Git, Deps, Costs or Coverage.
The menu item only appears for projects with a folder on your computer, not for built-in pages such as Gmail or Stats. The header says when the project was last analyzed; click Refresh to analyze it again now. Results are reused for up to 24 hours.
What each tab shows#
Overview: the headline numbers: source and test lines, Commits (30d), Total Spend, Tests, TODO / FIXME, Dependencies and Vulnerabilities. A warning appears at the top if possible secrets were found.
Files: source, test and other files, with lines and size per file type.
Health: TODO and FIXME notes, loosely typed code (
any), possible secrets and Large Files (>300 lines).Git: the last 30 days of commits, Churn Hotspots (90 Days), Knowledge Silos (files only one person changed in 90 days) and Stale Files (untouched for 6 months or more).
Deps: how many packages the project uses, which are outdated, and known vulnerabilities by severity.
Costs: what this project's sessions cost, with turns, time and tokens. The dollars mean the same as in Stats: API prices, not necessarily what you paid.
Coverage: how much of the code your tests run, and which files have no tests.
Fix what it finds#
Fix in Session on a finding starts a new session in the project, with a prompt asking the agent to fix it. That session uses your Claude plan. Copy Prompt copies the same prompt instead.
Ignore (the X on a finding) hides it from future reports. The "ignored (show)" link brings hidden ones back, and Restore puts one back for good.
Measure test coverage#
Open the Coverage tab.
Click Run Coverage. Yardmaster runs the project's tests and shows progress as it goes.
It works with projects tested by Vitest, Jest, pytest or Cargo. If a Vitest project lacks the coverage add-on, it offers Install & Run Coverage.
Analysis in the background#
To open instantly, Yardmaster analyzes your projects in the background, one at a time, only after their files change, and it holds back when your computer is busy. It skips the package check, which needs the internet. To stop it, turn this off in Settings > Diagnostics:
Check packages for known problems (Preview)#
The first scan downloads a security database for the kinds of packages your project uses (about 200 MB for JavaScript packages). Scan now checks again; Mute hides a finding you have looked at.
What goes over the internet. The Deps numbers come from your package manager's own audit and outdated checks, which ask the package registry. Everything else is read from your folder and git on this computer.
What it costs. Analyzing is free. Only Fix in Session uses AI.
Projects without git show no Git data; projects without a supported package file show no Deps data.
Related
- Check your code with RepoGuardRepoGuard is a built-in plugin that scans a project for security problems, leaked secrets and risky dependencies, grades it, and can start an agent to fix what it found.
- See and remove your stored keysStored Keys lists every API key and secret Yardmaster keeps on this computer, by name only, so you can find, replace or delete them without ever showing a value.