Code Health
See exactly where your codebase is getting worse and why
Security vulnerabilities, test gaps, dead code, duplication, runtime risks. Every finding links to the exact file and line, so you know what to fix and where.
Find the problems that actually matter before they hit production
Security vulnerabilities, runtime risks, and test gaps surface first because they're the ones that break things. Style nitpicks are there but they won't drown out real issues.
- Spot dead code, duplication, and inconsistent patterns before they spread across the codebase.
- Surface compliance violations and security issues the moment they're introduced, not after an audit.
- Track test gaps and weak assertions that quietly increase the cost of every future change.
Eight things that make or break a codebase
Each one is tracked continuously. When any of them starts degrading, you'll know before it becomes expensive to fix.
Security
Catch vulnerabilities, hardcoded secrets, and injection risks before they ship to production
Runtime
Find performance bottlenecks, missing error handling, and resource leaks that cause outages
Tests
Know if your tests actually catch bugs or just exist to hit a coverage number
Code Quality
Spot the code that's getting harder to change, before it slows everyone down
Duplication
Find copy-pasted logic before it becomes five places you need to update instead of one
Dead Code
Clean out unused functions and orphaned modules that confuse new devs and AI agents alike
Consistency
See where patterns are drifting so new devs and AI agents write code that fits
Compliance
Surface licensing violations and regulatory issues before they become legal problems
Catch quality drift before it becomes tech debt
Every assessment is tracked over time. Drift alerts fire the moment a category drops below its baseline. Not three sprints later when someone finally notices.
- Issue volume trends show whether debt is accumulating or burning down, week over week.
- Growth-vs-quality charts reveal if new code is introducing problems faster than old ones get fixed.
- Drift alerts trigger on category-level regressions. You'll know security slipped before the sprint ends.
See if debt is piling up or getting paid down
A snapshot tells you where things stand today. Trends tell you if they're getting better or worse. You'll know if new code is introducing problems faster than old ones get fixed.
- Find the files that change the most. Those are the hotspots most likely to break next.
- See where duplicated logic is spreading and where consolidation would actually save time.
- Know what percentage of changes improve the codebase vs. just piling on more code.
- Track whether your team's patterns are getting more consistent or less over time.
Your tests have coverage. But do they actually catch bugs?
80% coverage means nothing if assertions are shallow and mocks replace every real dependency. Octokraft measures test effectiveness, not just test existence.
- Assertion density. How many meaningful checks per test, not just 'expect(true).toBe(true)'.
- Test-to-code ratio. The balance between production code and the tests that guard it.
- Mock patterns. Flags tests that mock so aggressively they're only testing the mocks themselves.
- Structural coverage. Which code paths are actually exercised, not just imported.
Quality just drifts. Unless you're measuring it.
Get a real score, not a dashboard full of vanity metrics. See what's degrading, why it happened, and where to focus first.
Try Octokraft