ovecc health
Code-health hotspots at function granularity: functions over the complexity thresholds (McCabe cyclomatic and SonarSource cognitive), plus oversized units (long functions, long parameter lists). Complexity is computed by the native TS/JS extractor.
Usage: ovecc health [OPTIONS]
Example
$ ovecc health
Code health: 1 high-complexity function(s), 0 oversized unit(s)
[High] High complexity: validateOrder (cyclomatic 24, cognitive 32)
src/services/orders.ts:8 (cyclomatic 24, cognitive 32)
A clean run says so explicitly:
Code health: 0 high-complexity function(s), 0 oversized unit(s)
(no functions over the complexity or size thresholds)
What's measured
| Signal | Rule | Thresholds |
|---|---|---|
| Cyclomatic complexity | complexity | medium/high (per-function McCabe) |
| Cognitive complexity | complexity | medium/high (per-function SonarSource) |
| Long function | long-function | 75 lines (low) / 150 lines (medium) |
| Long parameter list | long-parameter-list | 7 params (low) / 10 params (medium) |
Repo-wide aggregates (max_cyclomatic, max_cognitive, total_cognitive,
high_complexity_functions, functions) are recorded at every index and trendable
via history.
Options
The global options only.
Related
review— flags new high-complexity functions per changehotspots— complexity as one signal among churn/coupling/ownership- Metrics reference