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 for github/gh-aw on 2026-07-06. The overall quality score is 79.2/100 (Good), up +8.0% over the last 7 days, driven by improved churn stability and strong documentation coverage. The codebase totals 1.85M LOC across 5,819 tracked files, with an exceptional test-to-source ratio of 1.96 (Go test LOC nearly 2× source). Growth is steady (~+1.8% LOC/7d, +13.3%/30d) — expansion is deliberate, not runaway.
Two areas warrant attention. Code organization scores only 13.6/25: there are 932 files over 500 LOC (a volatile metric inflated partly by generated .lock.yml workflow bundles). Comment density remains low at 9.86% (4.9/10). Source churn cooled this week — net change fell 43% to +25,729 lines across 1,023 files — reflecting a calmer, more stable development cycle after a busy prior week.
📊 Visualizations
Test coverage and documentation are maxed out; code organization and comment density are the two components dragging the score.
30-day view: LOC climbs steadily while the quality score holds in the 73–79 band and test ratio stays flat near 1.96.
YAML (27%) leads — dominated by generated .lock.yml workflow bundles — followed by Go tests and CJS JavaScript; hand-written Go source is 238k LOC.
pkg/ (760k) and .github/ (610k) hold the bulk of the codebase; docs/ at 106k reflects healthy documentation investment.
468k test LOC vs 238k source LOC — a 1.96 ratio, well above the recommended 0.5–1.0 band. Testing discipline is a clear strength.
Top source-file churn (7d, excluding generated files): the dashboard app.js saw a large net reduction (−3.7k), signaling refactoring/cleanup rather than growth.
Methodology: churn stability uses source-code churn only; generated files (*.lock.yml, actions-lock.json) are excluded from the score and tracked separately.
Recommendations
Tackle large files — 932 files exceed 500 LOC. Audit the top hand-written offenders in pkg/ and split cohesive units; this is the single biggest lever on the score (code organization is only 54%).
Raise comment density — at 9.86% (4.9/10), add doc comments on exported Go symbols in high-traffic packages to lift the weakest scoring component.
Sustain the calmer churn — net source change dropped 43% this week; keep large refactors (like the dashboard app.js cleanup) landing in reviewable chunks to hold churn stability above 70%.
Preserve the testing edge — the 1.96 test ratio is a genuine strength; keep new pkg/ code paired with tests to defend the maxed-out coverage component.
Watch the large-file metric noise — its 7d swing (525→932) is driven partly by generated bundles; consider excluding .lock.yml from the large-file count for a cleaner organization signal.
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 for github/gh-aw on 2026-07-06. The overall quality score is 79.2/100 (Good), up +8.0% over the last 7 days, driven by improved churn stability and strong documentation coverage. The codebase totals 1.85M LOC across 5,819 tracked files, with an exceptional test-to-source ratio of 1.96 (Go test LOC nearly 2× source). Growth is steady (~+1.8% LOC/7d, +13.3%/30d) — expansion is deliberate, not runaway.
Two areas warrant attention. Code organization scores only 13.6/25: there are 932 files over 500 LOC (a volatile metric inflated partly by generated
.lock.ymlworkflow bundles). Comment density remains low at 9.86% (4.9/10). Source churn cooled this week — net change fell 43% to +25,729 lines across 1,023 files — reflecting a calmer, more stable development cycle after a busy prior week.📊 Visualizations
Test coverage and documentation are maxed out; code organization and comment density are the two components dragging the score.
30-day view: LOC climbs steadily while the quality score holds in the 73–79 band and test ratio stays flat near 1.96.
YAML (27%) leads — dominated by generated
.lock.ymlworkflow bundles — followed by Go tests and CJS JavaScript; hand-written Go source is 238k LOC.pkg/(760k) and.github/(610k) hold the bulk of the codebase;docs/at 106k reflects healthy documentation investment.468k test LOC vs 238k source LOC — a 1.96 ratio, well above the recommended 0.5–1.0 band. Testing discipline is a clear strength.
Top source-file churn (7d, excluding generated files): the dashboard
app.jssaw a large net reduction (−3.7k), signaling refactoring/cleanup rather than growth.📈 Detailed Metrics
Size
Top directories:
pkg759,622 ·.github610,370 ·actions302,520 ·docs105,769 ·scratchpad36,143Quality
Tests
Churn — Source (7d, excludes
*.lock.yml&actions-lock.json)Churn — Generated files (informational only)
Workflows & Docs
.mdfiles.lock.ymlfilesQuality Score Breakdown
Methodology: churn stability uses source-code churn only; generated files (
*.lock.yml,actions-lock.json) are excluded from the score and tracked separately.Recommendations
pkg/and split cohesive units; this is the single biggest lever on the score (code organization is only 54%).app.jscleanup) landing in reviewable chunks to hold churn stability above 70%.pkg/code paired with tests to defend the maxed-out coverage component..lock.ymlfrom the large-file count for a cleaner organization signal.References: §28816127677
Beta Was this translation helpful? Give feedback.
All reactions