[daily-code-metrics] Daily Code Metrics Report - 2026-06-13 #39138
Replies: 2 comments
-
|
Smoke grunt. Bot poke discussion. Fire good. Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "safebrowsingohttpgateway.googleapis.com"
- "www.google.com"See Network Configuration for more information.
|
Beta Was this translation helpful? Give feedback.
-
|
Me test. Smoke test ran. Warning Firewall blocked 6 domainsThe following domains were blocked by the firewall during workflow execution:
network:
allowed:
- defaults
- "accounts.google.com"
- "android.clients.google.com"
- "clients2.google.com"
- "contentautofill.googleapis.com"
- "safebrowsingohttpgateway.googleapis.com"
- "www.google.com"See Network Configuration for more information.
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Key metrics today: LOC: 1,714,666 | Quality score: 73.5/100 (Good) | Test ratio: 2.00 | Active source files (7d): 1,155
The codebase continues a steady growth trajectory, adding +3.9% total LOC over the last 7 days and +15.8% over 30 days — now at 1.71M lines across 5,166 text files. Go remains the engineering core (660K lines, 2,218 files, 13,791 functions), while YAML (473K, largely generated workflow lock files) is the single largest line category. The overall quality score is 73.5/100 ("Good"), down 0.5 from yesterday and ~1.7 points below the 75.2 recorded when scoring began on 2026-06-08.
The score movement is driven by two components. Churn stability (3.8/15) is the weakest area: 1,155 source files were modified across 454 commits this week (the highest in the tracked window), reflecting intense, broad refactoring activity. Test-to-source ratio held at a very healthy 2.00 but is drifting down (−0.8% 7d, −4.7% 30d) as source code grows faster than test code — worth watching, though coverage remains well above the 0.5–1.0 recommended band. Test coverage, code organization, and documentation components are all stable.
Separately, generated
*.lock.ymlworkflow files saw enormous churn (+88,862/−54,167 across 249 files) but are correctly excluded from the quality score to avoid penalizing generated noise.📊 Visualizations
Quality Score Breakdown
Test Coverage is maxed (30/30), and Code Organization is strong (20.9/25 — only 16% of Go files exceed 500 LOC). The clearest improvement opportunities are Churn Stability (25% of max) and Comment Density (50% of max, 9.95% comment ratio).
Historical Trends (30 Days)
Total LOC climbs steadily (blue) while the test-to-source ratio (red) declines gradually — source is outpacing tests. Quality score (green, available since 06-08) sits in a tight 73.4–75.2 band.
📈 Detailed Metrics
Size
Quality
Test Coverage
Code Churn — Source (Last 7 Days, excludes *.lock.yml)
Most active source files: pkg/agentdrain/data/default_weights.json (+3,961/−5,642), docs/package-lock.json (+607/−3,291), actions/setup/js/package-lock.json (+1,822/−1,804), actions/setup/js/handle_agent_failure.test.cjs (+1,155/−602), pkg/workflow/js/safe_outputs_tools.json (+891/−631)
Workflow Lock File Churn (*.lock.yml only — informational)
Lock file churn is reported separately and excluded from the quality score.
Workflows
Documentation
Quality Score: 73.5/100 (Good)
History: 75.2 (06-08) → 73.4 → 73.9 → 74.0 → 73.5 (06-13)
💡 Insights & Recommendations
pkg/agentdrain/data/default_weights.jsonand thehandle_agent_failure/copilot_sdk_drivermodules dominate churn; consolidating these would lift the weakest score component (churn stability, 3.8/15).docs/keeps documentation coverage from slipping.References:
Report generated by Daily Code Metrics workflow · Historical data: 49 days · Last updated: 2026-06-13 UTC
Beta Was this translation helpful? Give feedback.
All reactions