You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Codebase health is stable and Good today. The repository holds 1,820,931 LOC across 5,736 files, up +3.0% over 7 days and +14.0% over 30 days — sustained, healthy growth rather than a spike. The composite quality score is 75.0/100 (Good), essentially flat over 30 days (75.0 → 73.3 → 76.1 → 75.0), signalling that quality is keeping pace with volume.
Test coverage remains the standout strength: 460,887 test LOC against 234,439 source LOC gives a test-to-source ratio of 1.97 — nearly 2 lines of test per line of Go source, earning the full 30/30 on that component. Documentation also grew strongly (+47.9% doc files in 30d, 519 files / 84,763 LOC). The weakest components are comment density (4.9/10) and code organization (13.3/25).
One measurement caveat worth flagging: the 7-day "source" churn (1,249 files, 439 commits, +71,744 / −34,068) is dominated by vendored and generated artifacts — minified app.js/app.ts dashboard bundles and multiple package-lock.json files (each showing net ≈ 0, i.e. reformatted rather than authored). Real hand-written Go volatility is much lower. See the recommendations for tightening this.
📊 Visualizations
Language mix is led by YAML (491K, 27%) and Go Tests (461K, 25%), then JavaScript/CJS and Markdown. Go source itself is 234K (13%). The heavy YAML share reflects the 258 compiled .lock.yml workflow files — expected for this project.
pkg/ (~733K) and .github/ (~600K, mostly compiled workflows) dominate, with actions/ and docs/ next. Core Go logic concentrates in pkg/, consistent with the CLI/compiler architecture.
Test Coverage is maxed (30/30) and Documentation is strong (18.1/20, 90%). Comment Density (4.9/10) and Code Organization (13.3/25) are the clearest improvement levers.
At a 1.97 test-to-source ratio the project is well above the recommended 0.5–1.0 band — a genuine strength, though the ratio has drifted down slightly (−3.2% over 30d) as source grows marginally faster than tests.
The top 7-day changes (excluding *.lock.yml and actions-lock.json) are almost entirely generated bundles and package-lock.json with net ≈ 0. The only substantive hand-authored deltas are cli/audit.go (+666/−637) and cli/forecast.go (removed, −1,247).
LOC climbs steadily (+14% / 30d) while the quality score and test ratio hold flat — growth without quality regression.
📈 Detailed Metrics
Size
Language
LOC
Share
YAML
491,040
27.0%
Go Tests
460,887
25.3%
JavaScript (CJS)
276,000
15.2%
Markdown
263,028
14.4%
Go Source
234,439
12.9%
JSON
55,424
3.0%
Directory
LOC
pkg
733,355
.github
600,374
actions
297,098
docs
102,269
Metrics & Trends
Category
Metric
Current
7d
30d
Size
LOC total
1,820,931
⬆️ +3.0%
⬆️ +14.0%
Size
Total files
5,736
⬆️ +4.8%
⬆️ +14.5%
Size
Go files
2,367
⬆️ +3.2%
⬆️ +11.8%
Tests
test_lines_of_code
460,887
⬆️ +2.4%
⬆️ +8.7%
Tests
test_to_source_ratio
1.966
➡️ −0.5%
➡️ −3.2%
Quality
function_count
15,163
⬆️ +5.3%
⬆️ +18.1%
Quality
comment_ratio
9.83%
➡️ −1.0%
➡️ −3.1%
Quality
large_files_over_500
966
⚠️ noisy
⚠️ noisy
Quality
avg_file_size_go_source
235.9
➡️ −0.6%
➡️ −1.2%
Docs
doc_files
519
⬆️ +12.6%
⬆️ +47.9%
Docs
doc_loc
84,763
⬆️ +6.9%
⬆️ +23.7%
Docs
code_to_docs_ratio
2.77
➡️ −3.5%
— *
Workflows
total (.md)
355
➡️ +2.0%
— *
Workflows
lock_yml_files
258
⬆️ +2.8%
⬆️ +9.3%
Workflows
avg_workflow_size
233.9
➡️ +0.4%
—
* 30-day baselines for a few derived ratios used an earlier calculation method, so those comparisons are omitted rather than shown misleadingly. The large_files_over_500 counter is measurement-noisy (bounces 519↔966 day-to-day) and is not treated as a real signal.
259 files · +60,979 / −49,998 · net +10,981 — tracked separately; not included in the quality score.
Quality Score: 75.0/100 (Good)
Test Coverage (30%): 30.0/30
Code Organization (25%): 13.3/25
Documentation (20%): 18.1/20
Churn Stability (15%): 8.7/15
Comment Density (10%): 4.9/10
💡 Insights & Recommendations
Tighten churn measurement — the "source" churn is swamped by vendored package-lock.json files and minified dashboard bundles (app.js/app.ts, net ≈ 0). Add package-lock.json and the compiled *.min.js/dashboard bundle paths to the churn exclusion list so the metric reflects real Go/authored volatility. This will also make Churn Stability (currently 8.7/15) a more meaningful signal.
Improve comment density — the weakest component (4.9/10, comment ratio 9.83% and slowly declining). Prioritize doc comments on exported Go symbols in pkg/, where most core logic lives.
Watch the test-ratio drift — still excellent at 1.97, but down −3.2% over 30d as source outgrows tests. Keep adding tests alongside new pkg/ and cli/ code to hold the ratio near 2.0.
Stabilize the large-file counter — large_files_over_500 swings 519↔966 between runs, indicating an inconsistent measurement rather than real change. Fix the counting method so Code Organization (13.3/25) trends reliably.
Sustain documentation momentum — doc files grew +47.9% in 30d; the code-to-docs ratio (2.77) is healthy. Keep docs in step with the ongoing +14%/30d code growth.
Report generated by Daily Code Metrics workflow Historical data: 30 days | Last updated: 2026-07-01 19:20 UTC
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Codebase health is stable and Good today. The repository holds 1,820,931 LOC across 5,736 files, up +3.0% over 7 days and +14.0% over 30 days — sustained, healthy growth rather than a spike. The composite quality score is 75.0/100 (Good), essentially flat over 30 days (75.0 → 73.3 → 76.1 → 75.0), signalling that quality is keeping pace with volume.
Test coverage remains the standout strength: 460,887 test LOC against 234,439 source LOC gives a test-to-source ratio of 1.97 — nearly 2 lines of test per line of Go source, earning the full 30/30 on that component. Documentation also grew strongly (+47.9% doc files in 30d, 519 files / 84,763 LOC). The weakest components are comment density (4.9/10) and code organization (13.3/25).
One measurement caveat worth flagging: the 7-day "source" churn (1,249 files, 439 commits, +71,744 / −34,068) is dominated by vendored and generated artifacts — minified
app.js/app.tsdashboard bundles and multiplepackage-lock.jsonfiles (each showing net ≈ 0, i.e. reformatted rather than authored). Real hand-written Go volatility is much lower. See the recommendations for tightening this.📊 Visualizations
Language mix is led by YAML (491K, 27%) and Go Tests (461K, 25%), then JavaScript/CJS and Markdown. Go source itself is 234K (13%). The heavy YAML share reflects the 258 compiled
.lock.ymlworkflow files — expected for this project.pkg/(~733K) and.github/(~600K, mostly compiled workflows) dominate, withactions/anddocs/next. Core Go logic concentrates inpkg/, consistent with the CLI/compiler architecture.Test Coverage is maxed (30/30) and Documentation is strong (18.1/20, 90%). Comment Density (4.9/10) and Code Organization (13.3/25) are the clearest improvement levers.
At a 1.97 test-to-source ratio the project is well above the recommended 0.5–1.0 band — a genuine strength, though the ratio has drifted down slightly (−3.2% over 30d) as source grows marginally faster than tests.
The top 7-day changes (excluding
*.lock.ymlandactions-lock.json) are almost entirely generated bundles andpackage-lock.jsonwith net ≈ 0. The only substantive hand-authored deltas arecli/audit.go(+666/−637) andcli/forecast.go(removed, −1,247).LOC climbs steadily (+14% / 30d) while the quality score and test ratio hold flat — growth without quality regression.
📈 Detailed Metrics
Size
Metrics & Trends
* 30-day baselines for a few derived ratios used an earlier calculation method, so those comparisons are omitted rather than shown misleadingly. The
large_files_over_500counter is measurement-noisy (bounces 519↔966 day-to-day) and is not treated as a real signal.Churn — Source (7d, excludes
*.lock.yml&actions-lock.json)1,249 files · 439 commits · +71,744 / −34,068 · net +37,676Most active (net authored change is much smaller — top entries are reformatted vendored bundles):
...dashboard/web/app.js(bundle)...eslint-factory/package-lock.jsoneslint-factory/package-lock.jsoncli/audit.gocli/forecast.go(removed)Churn — Generated (7d,
*.lock.yml+actions-lock.json, informational only)259 files · +60,979 / −49,998 · net +10,981— tracked separately; not included in the quality score.Quality Score: 75.0/100 (Good)
💡 Insights & Recommendations
package-lock.jsonfiles and minified dashboard bundles (app.js/app.ts, net ≈ 0). Addpackage-lock.jsonand the compiled*.min.js/dashboard bundle paths to the churn exclusion list so the metric reflects real Go/authored volatility. This will also make Churn Stability (currently 8.7/15) a more meaningful signal.pkg/, where most core logic lives.pkg/andcli/code to hold the ratio near 2.0.large_files_over_500swings 519↔966 between runs, indicating an inconsistent measurement rather than real change. Fix the counting method so Code Organization (13.3/25) trends reliably.Report generated by Daily Code Metrics workflow
Historical data: 30 days | Last updated: 2026-07-01 19:20 UTC
Beta Was this translation helpful? Give feedback.
All reactions