[daily-code-metrics] Daily Code Metrics Report - 2026-05-14 #32208
Closed
Replies: 1 comment
-
|
This discussion has been marked as outdated by Daily Code Metrics and Trend Tracking Agent. A newer discussion is available at Discussion #32464. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The gh-aw codebase grew to 1,481,323 total LOC (+4.9% over 7 days, +17.3% over 30 days) with substantial activity: 1,029 source files modified across 394 commits in the last week (+53,945 / -11,571 source lines, net +42,374). The repo continues to add Go source (+4.8% in 7d), workflow YAML (+8.1%), and a notable JSON growth spike (+11.8%) driven by
pkg/agentdrain/data/default_weights.jsonand editor autocomplete data.Today's quality score lands at 63/100 ("Fair") — down from 82 a week ago and 72 a month ago. The drop is driven by elevated source-code volatility (
churn stabilitycomponent at 4.7/15) and an organization penalty from 328 files now exceeding 500 LOC. Test-to-source ratio remains very healthy at 2.10, well above the recommended 0.5–1.0 band, while comment density holds at 10.46%.Worth flagging: TypeScript LOC dropped −55.7% in 7 days (2,437 → 1,079), which looks like a directory restructure rather than removal of behavior; Python grew +269% (829 → 3,060) from the new
aw_yield_precompute.pyand related scripts.📊 Visualizations
Historical Trends (24 days)
Total LOC has trended upward steadily; quality score has been volatile, swinging between the high 60s and low 80s as churn stability fluctuates with weekly activity. The test-to-source ratio is mildly declining (-3.8% vs 30d ago) but remains far above target. Today's reading sits at the lower end of recent quality scores — worth watching whether tomorrow's run rebounds.
Quality Score Breakdown
Test coverage (30/30) and comment density (10/10) are maxed out. The drag comes from code organization (4.5/25 — too many >500-LOC files), documentation (13.6/20 — could improve coverage-to-code ratio), and churn stability (4.7/15 — high source volatility this week).
LOC Distribution by Language
Go Tests dominate (401k, 27.1%), followed by YAML config (382k, 25.8%) reflecting the workflow-heavy nature of the repo. Markdown documentation is the third-largest pile (232k, 15.7%) — this codebase is unusually documentation- and config-heavy relative to the Go source itself (191k).
Top Directories by LOC
pkg/(631k, 42.7%) and.github/workflows/(456k, 30.8%) account for nearly three-quarters of the codebase.actions/(220k) anddocs/(80k) are the next layers.cmd/remains intentionally thin at 2,443 LOC, signaling good separation between thin entrypoints and the bulk of business logic inpkg/.Code Churn — Last 7 Days (excludes
*.lock.yml)pkg/agentdrain/data/default_weights.jsonsaw the largest source churn (+4502/-1146), followed by editor autocomplete data and the new forecast feature (pkg/cli/forecast.go+1150/-8).README.mdis the only file with major deletions (+176/-931) — likely a documentation restructure.Test Coverage Analysis (chart not embedded — asset limit reached at 5/5)
📈 Detailed Metrics
Size Metrics
Lines of Code by Language
Lines of Code by Directory
Quality Indicators
Test Coverage
test_lines_of_code): 401,196test_to_source_ratio): 2.10Code Churn (Last 7 Days)
Source Code Churn (excludes
*.lock.yml)Most Active Source Files
pkg/agentdrain/data/default_weights.json: +4,502 / −1,146docs/public/editor/autocomplete-data.json: +1,911 / −954scripts/aw_yield_precompute.py: +1,337 / −27pkg/cli/forecast.go: +1,150 / −8docs/src/content/docs/reference/forecast-specification.md: +1,044 / −39specs/safe-output-outcome-evaluation.md: +571 / −0pkg/cli/add_package_manifest_test.go: +538 / −0pkg/workflow/central_slash_command_workflow.go: +514 / −26.github/workflows/outcome-collector.md: +346 / −228README.md: +176 / −931Workflow Lock File Churn (
*.lock.ymlonly, tracked separately)Lock file churn is reported here but excluded from quality score to avoid noise from generated files.
Workflow Metrics
Documentation
docs/*.md): 301 (+6.0% vs 7d)Quality Score: 63 / 100 — Fair
Trend Summary
💡 Insights & Recommendations
pkg/workflow/andpkg/cli/for splitting would move this component meaningfully. A 20% reduction in large files would raise the overall score from 63 → ~68.docs/and not lost — and if migrated, update cross-references inAGENTS.mdandCONTRIBUTING.md..github/workflows/growth (+8.1% YAML in 7 days). The compiled.lock.ymlfiles added 28k net lines this week. Periodic audits to retire unused workflows would reduce CI surface area and review burden.docs/ARCHITECTURE.mdnote explaining the language choice forscripts/so future contributors don't re-introduce TS scripts.Report generated by Daily Code Metrics workflow
Historical data: 24 days available | Last updated: 2026-05-14 19:10 UTC
References: §25879592302
Beta Was this translation helpful? Give feedback.
All reactions