[daily-code-metrics] Daily Code Metrics Report - 2026-06-20 #40499
Replies: 1 comment 1 reply
-
|
/q make sure code generated files like lock.yml are EXCLUDED from report. actions-lock.json are also code generated. |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Key metrics today: LOC: 1,740,168 | Quality score: 77.3/100 (Good) | Test ratio: 1.98 | Active source files (7d): 990
📋 Executive Summary
The
gh-awcodebase continues its steady growth, reaching 1.74M lines of code across 11 languages, up +1.5% in 7 days and +13.2% over 30 days. The overall quality score sits at 77.3/100 ("Good"), improving +5.2% week-over-week — driven primarily by stronger churn stability as weekly file activity settled from last week's peak. Test coverage remains the standout strength (full 30/30 points, test:source ratio of 1.98), and documentation scores well (17.4/20) on a healthy 2.87 code-to-docs ratio.Activity over the last 7 days was substantial but stable: 269 commits touching 990 source files for a net +26,323 lines. The biggest churn concentrates in generated/config artifacts (
action_pins.json,safe_outputs_tools.json) and specs/reference docs rather than core Go logic, which signals healthy, low-risk volatility. Separately,*.lock.ymlworkflow files saw heavy regeneration (253 files, net −723) — correctly excluded from the quality score to avoid generated-file noise.The two areas with the most headroom are comment density (9.96%, worth only 5.0/10) and code organization (14.8/25). The organization score reflects a rising count of files over 500 LOC, though that specific metric has been measured inconsistently across historical runs and should be read as directional rather than precise.
📊 Key Visualizations
Quality Score Breakdown
Test Coverage is maxed out (100% of weight); Documentation (87%) and Churn Stability (67%) are solid. The clearest upside is Comment Density (50%) and Code Organization (59%) — together ~15 unrealized points.
Historical Trends (30 Days)
LOC rises consistently (7-day MA climbing steadily), while the test:source ratio has drifted down slightly (−4.1% over 30d) as source code grew a touch faster than tests. The quality score has been stable-to-improving across the days where it's been tracked (mid-70s).
💡 Top Recommendations
pkg/(40.9% of LOC) to lift this toward the 20% full-marks threshold.pkg/code to hold the ratio above 1.5.📈 Detailed Metrics
Size Metrics
Quality Indicators
Test Coverage
test_lines_of_code): 446,760 (7d ⬆️ +1.6% | 30d ⬆️ +8.4%)test_to_source_ratio): 1.984 (7d ➡️ −0.8% | 30d ⬇️ −4.1%)Code Churn (Last 7 Days — source only, excludes
*.lock.yml)Most Active Source Files:
pkg/workflow/js/safe_outputs_tools.json(+915/−843)specs/otel-observability-spec.md(+862/−779)docs/src/content/docs/reference/frontmatter-full.md(+1,225/−118).github/aw/actions-lock.json(+687/−622)pkg/actionpins/data/action_pins.json(+687/−622)pkg/workflow/data/action_pins.json(+687/−622)Workflow Lock File Churn (
*.lock.ymlonly)Lock file churn is reported separately and excluded from quality score calculations to avoid noise from generated files.
Workflow Metrics
total_workflows): 347 (7d ➡️ +1.2% | 30d ⬆️ +6.8%)Documentation
Quality Score: 77.3/100 (Good)
Quality score uses standardized, documented formulas (test:source ratio, large-file share, code-to-docs ratio, source-churn intensity, comment ratio). Churn stability uses source churn only, excluding
*.lock.yml.References: §27880617477
Report generated by Daily Code Metrics workflow (executive summary variant)
Historical data: 53 entries | Last updated: 2026-06-20 UTC
Beta Was this translation helpful? Give feedback.
All reactions