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
The gh-aw codebase reached 1,862,370 LOC across 5,937 files today (2026-07-08), continuing steady growth of +2.3% in 7 days and +11.1% over 30 days. The composite quality score is 71.9/100 (⬇️ −4.1% 7d), sitting just below the ~72–78 band the repo has held all month. The dip is driven almost entirely by churn: source-code churn stayed elevated at +49,026 / −16,045 lines (net +32,981) across 1,071 files this week, which pulls the churn-stability component down to 7.6/15. Everything else is stable-to-improving.
Test investment remains the standout strength — 471,668 test LOC against 240,299 Go source LOC gives a 1.96 test-to-source ratio, saturating the 30-point test-coverage component. Documentation also continues to expand meaningfully: 557 doc files / 85,160 doc LOC (⬆️ +7.3% files in 7d, +45.1% in 30d), keeping the source-to-docs ratio at a healthy 2.82. Workflow surface grew to 359 .md workflows and 259 .lock.yml compiled outputs.
The main watch-items are churn concentration (a few large JSON/data regenerations dominate the week) and code organization: 938 files now exceed 500 LOC (15.8% of all files), holding the organization component at 11.8/25. Comment density (9.86%, 6.6/10) is steady but remains the smallest lever for quality-score improvement.
📊 Visualizations
YAML (503k) and Go Tests (472k) lead the codebase; Go source is 240k, so tests outweigh source ~2:1.
pkg/ (753k) and .github/ (614k, mostly compiled workflow locks) hold the bulk of the code; docs/ is a substantial 106k.
Test coverage is maxed (30/30); churn stability (7.6/15) and comment density (6.6/10) are the components furthest from target.
At 1.96× source, test volume comfortably exceeds the recommended 0.5–1.0 band — mature test discipline.
Top source churn is dominated by regenerated action_pins.json data files and a large remote_fetch.go refactor (net −1,547).
LOC climbs steadily while the quality-score 7-day moving average holds ~75; the test ratio drifts down slowly as source grows.
1 The 30-day jump in large-file count outpaces LOC/file growth and likely reflects a counting-methodology change earlier in the history window; the 7-day trend (−2.9%) is the reliable signal.
Quality Score Breakdown — 71.9 / 100
Component
Weight
Score
Notes
Test coverage
30%
30.0
Saturated (1.96× ratio)
Code organization
25%
11.8
938 files >500 LOC (15.8%)
Documentation
20%
15.9
Source-to-docs 2.82
Churn stability
15%
7.6
Elevated source churn (net +32,981)
Comment density
10%
6.6
9.86% comment ratio
Recommendations
Tame source churn — the week's net +32,981 is inflated by regenerated data (action_pins.json in two locations, models.json). Confirm these are gitignore/lockfile-appropriate or consolidate to a single source of truth so they stop dominating churn-stability scoring.
Split the largest files — 938 files now exceed 500 LOC. Targeting the top offenders in pkg/ would directly lift the code-organization component (currently 11.8/25).
Nudge comment density — at 9.86%, doc-comments on exported Go symbols in high-traffic pkg/ packages are the cheapest path toward the 15% target (6.6→ higher on the 10-pt component).
Guard the test ratio — source grew +2.5% vs tests +2.3% this week; keep test additions ahead of source so the 1.96× ratio doesn't erode.
Watch remote_fetch.go — a net −1,547 refactor this week; verify coverage held through the change.
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.
-
The gh-aw codebase reached 1,862,370 LOC across 5,937 files today (2026-07-08), continuing steady growth of +2.3% in 7 days and +11.1% over 30 days. The composite quality score is 71.9/100 (⬇️ −4.1% 7d), sitting just below the ~72–78 band the repo has held all month. The dip is driven almost entirely by churn: source-code churn stayed elevated at +49,026 / −16,045 lines (net +32,981) across 1,071 files this week, which pulls the churn-stability component down to 7.6/15. Everything else is stable-to-improving.
Test investment remains the standout strength — 471,668 test LOC against 240,299 Go source LOC gives a 1.96 test-to-source ratio, saturating the 30-point test-coverage component. Documentation also continues to expand meaningfully: 557 doc files / 85,160 doc LOC (⬆️ +7.3% files in 7d, +45.1% in 30d), keeping the source-to-docs ratio at a healthy 2.82. Workflow surface grew to 359
.mdworkflows and 259.lock.ymlcompiled outputs.The main watch-items are churn concentration (a few large JSON/data regenerations dominate the week) and code organization: 938 files now exceed 500 LOC (15.8% of all files), holding the organization component at 11.8/25. Comment density (9.86%, 6.6/10) is steady but remains the smallest lever for quality-score improvement.
📊 Visualizations
YAML (503k) and Go Tests (472k) lead the codebase; Go source is 240k, so tests outweigh source ~2:1.
pkg/(753k) and.github/(614k, mostly compiled workflow locks) hold the bulk of the code;docs/is a substantial 106k.Test coverage is maxed (30/30); churn stability (7.6/15) and comment density (6.6/10) are the components furthest from target.
At 1.96× source, test volume comfortably exceeds the recommended 0.5–1.0 band — mature test discipline.
Top source churn is dominated by regenerated
action_pins.jsondata files and a largeremote_fetch.gorefactor (net −1,547).LOC climbs steadily while the quality-score 7-day moving average holds ~75; the test ratio drifts down slowly as source grows.
📈 Detailed Metrics
Size
pkg/752,845Quality
Tests
Churn — Source (7d, excl.
*.lock.yml/actions-lock.json)Churn — Generated files (7d,
*.lock.yml/actions-lock.jsononly)Workflows & Docs
.md).lock.yml1 The 30-day jump in large-file count outpaces LOC/file growth and likely reflects a counting-methodology change earlier in the history window; the 7-day trend (−2.9%) is the reliable signal.
Quality Score Breakdown — 71.9 / 100
Recommendations
action_pins.jsonin two locations,models.json). Confirm these are gitignore/lockfile-appropriate or consolidate to a single source of truth so they stop dominating churn-stability scoring.pkg/would directly lift the code-organization component (currently 11.8/25).pkg/packages are the cheapest path toward the 15% target (6.6→ higher on the 10-pt component).remote_fetch.go— a net −1,547 refactor this week; verify coverage held through the change.References: §28967651619
Beta Was this translation helpful? Give feedback.
All reactions