[daily-code-metrics] Daily Code Metrics Report - 2026-05-21 #33845
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 #34094. |
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.
-
Key metrics today: LOC: 1,537,014 | Quality score: 77/100 (Good) | Test ratio: 2.068 | Active source files (7d): 1,329
The codebase grew +2.81% week-over-week and +21.73% over the 30-day window — driven primarily by
.github/workflows(+3.5K LOC),pkg/(+5.7K LOC compared to a week ago), and continued Go source/test expansion (+4.3% / +2.7%). Quality score holds at 77/100 (Good): test coverage, documentation, and comment density all score at or near full marks, but churn stability (3/15) remains the weakest component — 1,329 source files modified and 483 commits in 7 days. Code organization (15/25) is pulled down by 338 Go files over 500 LOC.Notable: test-to-source ratio dipped slightly (-1.48% / 7d) as source code grew faster than tests this week — worth watching but still very healthy at 2.07x. Doc files +56% over 30 days reflects active documentation buildout. Workflow lock files churned heavily (234 files, +62K/-49K lines) but are excluded from quality scoring as generated artifacts.
📊 Key Visualizations
Quality Score Breakdown
Test coverage (30/30) and documentation (20/20) are at maximum. Churn stability (3/15) is the lowest-scoring component — driven by very high source modification volume this week. Code organization (15/25) is held back by the 338 Go files over 500 lines.
Historical Trends (30 Days)
Total LOC has climbed steadily from ~1.26M → ~1.54M (+22%) over the tracked window. Quality score 7-day MA improved from low-60s to high-70s over the period, while test-to-source ratio softened from ~2.18 → ~2.07 as source growth outpaced test growth.
📈 Detailed Metrics
Size Metrics
Lines of Code by Language
Top Directories by LOC
Quality Indicators
Test Coverage
test_lines_of_code): 412,005test_to_source_ratio): 2.068Code Churn (Last 7 Days)
Source Code Churn (Excludes *.lock.yml)
Most Active Source Files
pkg/parser/schemas/main_workflow_schema.json: +3,291 / -3,010docs/public/editor/autocomplete-data.json: +1,515 / -1,224pkg/workflow/gh_cli_permissions_test.go: +1,016 / -91actions/setup/js/create_pull_request.test.cjs: +926 / -77actions/setup/js/send_otlp_span.test.cjs: +881 / -27actions/setup/js/create_pull_request.cjs: +785 / -669specs/otel-observability-spec.md: +760 / -13pkg/workflow/testdata/TestWasmGolden_AllEngines/claude.golden: +711 / -8pkg/workflow/testdata/TestWasmGolden_AllEngines/codex.golden: +683 / -9actions/setup/js/safe_outputs_handlers.test.cjs: +678 / -55Workflow Lock File Churn (*.lock.yml only)
Note: Lock file churn is reported separately and excluded from quality score calculations to avoid noise from generated files.
Workflow Metrics
total_workflows): 325 (⬆️ +2.85% / 7d)Documentation
Quality Score: 77/100 (Good)
Component Breakdown
Trend Summary
💡 Insights & Recommendations
main_workflow_schema.jsonat +3,291/-3,010), or work fragmentation. If the latter, batching related changes into fewer PRs would improve reviewability.pkg/cli/forecast.go-style feature work that's landed recently.pkg/workflow/based on churn patterns) and consider splitting them as natural seams emerge..lock.ymlchurn as expected noise — 234 lock files churned with +62K/-49K lines. These are generated artifacts and correctly excluded from the quality score; no action needed.References:
Report generated by Daily Code Metrics workflow
Historical data: 30 days | Last updated: 2026-05-21 19:08 UTC
Beta Was this translation helpful? Give feedback.
All reactions