Code metrics analyzer
Total lines1
Non-empty lines0
TODO matches0
FIXME matches0
console.log(…)0
Lines w/ // or /* (approx)0
Comment heuristic is naive — use a real parser in CI for coverage gates.
Key takeaways
- Fast pre-review before opening a PR description.
- Surfaces lingering console.log for cleanup sprints.
- TODO/FIXME counts help prioritize tech debt tickets.
- Line counts help compare pasted snippets of different modules.
- Pair with your real linter for merge gates.
Who built this
ContractorHQ is edited by Bernard Guido — 25+ years in trade operations and software. These utilities follow the same quality bar as our reviews: fast pages, honest disclosure, and tools that stay useful without selling your data.
Frequently asked questions
Does this understand TypeScript types?
No AST — regex and line splits only. It is for quick gut checks before you open ESLint in CI.
Why approximate comments?
Inline URLs and strings can contain // without being comments. Treat that number as fuzzy.
Can I paste proprietary code?
It never leaves your machine, but follow your employer’s policy on local tooling anyway.
Will it run the code?
No execution — static counting only.