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
Metrics collected for 2026-11-13 — 2,300,450 LOC across 11,694 files; provisional quality score 95.3 / 100 (churn excluded). Churn data is unavailable: the clone is shallow and git fetch --unshallow fails on TLS certificate verification.
Key metrics today: LOC: 2,300,450 | Quality score: 95.3 (provisional) | Test ratio: 0.478 | Active files (7d): n/a (no churn data)
📊 Visualizations
Go holds 47.7% of LOC (1,098,014 lines), and JavaScript adds 23.2%.
pkg/workflow (657,724) and actions/setup (577,288) account for more than half of all LOC.
Documentation (97.2) and comment density (100.0) are strongest. Code organization (91.7) is the weakest scored component.
The test-to-source ratio is 0.478, stable against 2026-11-11 (0.477), and just under the 0.5 target used by the test-coverage score component.
Churn could not be computed because git history is shallow. The chart is a placeholder until the fetch succeeds.
LOC is 2,300,450, up 0.9% on 2026-11-11 and up 4.8% on 2026-11-07. Test-ratio values from 2026-10-31 to 2026-11-07 (~1.6, except 0.386 on 11-06) reflect a classification change and are excluded from the trend.
View Full Details
Trend and scope notes
Implausible swing (genuine change, needs investigation): LOC moved +11.6% on 2026-11-06 and −38.2% on 2026-11-07. The file count stayed near 11,000 (10,948 → 10,997). The cloc_command label changed on 2026-11-06 (lock files now excluded), which coincides with the first jump. The cause is not determined from the available data.
Baseline for 7d comparison: the 2026-11-06 entry (3,552,875) is part of the swing above, so it is not used as a baseline. Against 2026-11-07 (same label, stable file count), LOC is +4.8%.
30d: LOC before 2026-11-07 and the quality score before 2026-11-08 should not be used for 30-day deltas without recomputation.
Quality score breakdown (weighted; churn excluded and renormalised over 85%):
Component
Weight
Score
Weighted
Test coverage
30%
95.6
28.68
Code organization
25%
91.7
22.93
Documentation
20%
97.2 (carried forward)
19.44
Churn stability
15%
n/a (no churn data)
—
Comment density
10%
100.0 (ratio 0.102 vs target 0.10, capped)
10.00
Total
81.05 / 0.85 = 95.3
Tests
Metric
Value
Trend vs 2026-11-11
test_lines_of_code
744,362
⬆️ +1.1%
Test files
2,851
⬆️ +25
test_to_source_ratio
0.478
➡️ +0.2%
Churn — source (7d)
Unavailable: git fetch --unshallow failed with a TLS certificate verification error. Churn is null in every history entry (2026-10-20 to 2026-11-13).
Churn — generated files (7d)
Unavailable (same cause). The 371 *.lock.yml and actions-lock.json files are excluded from LOC.
Workflows and docs
Metric
Value
total_workflows (direct .github/workflows/*.md)
367 (⬆️ +2)
lockfile_count
367
Workflow name mismatch
0
Docs files (docs/)
1,450 (⬆️ +15)
Docs LOC
150,128 (⬆️ +0.5%)
Recommendations
Restore churn metrics. Give the metrics job full git history (for example, a checkout with fetch-depth: 0) so that git rev-parse --is-shallow-repository returns false. Do not disable TLS verification to get there.
Make LOC reproducible. Install cloc so the glossary-pinned command cloc --vcs=git --json --quiet . can run. Until then, the Python counter is a documented substitute, not the pinned method.
Investigate the 2026-11-06 / 2026-11-07 LOC swing (+11.6%, then −38.2%) with file count stable. This needs full git history to identify the responsible commits.
Reduce large files. 972 files exceed 500 non-blank lines (8.3%). Splitting the largest ones would lift code organization above 91.7.
Recompute documentation score. The 97.2 documentation component has been fixed since 2026-11-08 and should be recalculated.
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.
Summary
Metrics collected for 2026-11-13 — 2,300,450 LOC across 11,694 files; provisional quality score 95.3 / 100 (churn excluded). Churn data is unavailable: the clone is shallow and
git fetch --unshallowfails on TLS certificate verification.Key metrics today: LOC: 2,300,450 | Quality score: 95.3 (provisional) | Test ratio: 0.478 | Active files (7d): n/a (no churn data)
📊 Visualizations
Go holds 47.7% of LOC (1,098,014 lines), and JavaScript adds 23.2%.
pkg/workflow(657,724) andactions/setup(577,288) account for more than half of all LOC.Documentation (97.2) and comment density (100.0) are strongest. Code organization (91.7) is the weakest scored component.
The test-to-source ratio is 0.478, stable against 2026-11-11 (0.477), and just under the 0.5 target used by the test-coverage score component.
Churn could not be computed because git history is shallow. The chart is a placeholder until the fetch succeeds.
LOC is 2,300,450, up 0.9% on 2026-11-11 and up 4.8% on 2026-11-07. Test-ratio values from 2026-10-31 to 2026-11-07 (~1.6, except 0.386 on 11-06) reflect a classification change and are excluded from the trend.
View Full Details
Trend and scope notes
cloc_commandlabel changed on 2026-11-06 (lock files now excluded), which coincides with the first jump. The cause is not determined from the available data.Size
lines_of_code_totalcloc_commandpython git ls-files line counter, non-blank, excl lock files (cloc unavailable)cloc_file_countQuality
Quality score breakdown (weighted; churn excluded and renormalised over 85%):
Tests
test_lines_of_codetest_to_source_ratioChurn — source (7d)
Unavailable:
git fetch --unshallowfailed with a TLS certificate verification error. Churn is null in every history entry (2026-10-20 to 2026-11-13).Churn — generated files (7d)
Unavailable (same cause). The 371
*.lock.ymlandactions-lock.jsonfiles are excluded from LOC.Workflows and docs
total_workflows(direct.github/workflows/*.md)lockfile_countdocs/)Recommendations
fetch-depth: 0) so thatgit rev-parse --is-shallow-repositoryreturnsfalse. Do not disable TLS verification to get there.clocso the glossary-pinned commandcloc --vcs=git --json --quiet .can run. Until then, the Python counter is a documented substitute, not the pinned method.All reactions