scc report

golden-fixture

Generated by scc - Sloc, Cloc and Code.

01 Overview

Aggregate counts across all source files in the working tree, with cost estimates and ULOC-based DRYness.

Files
21
3 languages
SLOC
10,640
code lines
Comments
780
6.0%
Complexity
510
cyclomatic est.
ULOC
7,420
DRYness 56.9%
Bytes
524K
on disk
Code 81.6% Blank 12.4% Comment 6.0% 13,040 total lines

02 Languages · 3 detected

Per-language counts and share of total code. Bar shows code share; ULOC indicates how many lines are unique.

Language Files Code Comment Blank Complexity ULOC Share
Go 12 8,000 600 1,200 420 5,400
JavaScript 6 2,400 180 360 90 1,800
Markdown 3 240 0 60 0 220
Total 21 10,640 780 1,620 510 7,420

03 Line length

Distribution of characters per line, bucketed across all files. Helps spot files with unusually long lines.

4,200 0–20 3,800 20–40 1,600 40–60 700 60–80 220 80–100 100 100–120 20 120+
38.2 mean
220 longest line (chars)
2 outlier files tracked

04 Hotspots · top 3 of 3

Files with the highest churn × complexity. High score = touched often and hard to reason about, prime targets for refactoring or test coverage.

FileScoreCommitsAuthorsChurnComplexity
internal/server.go 92.5 64 4 1,200 240
internal/cache.go 41.2 28 2 420 120
web/app.js 17.8 14 2 180 60

05 Change coupling · top 3 of 3

File pairs that change together in the same commits. High coupling = an implicit dependency git enforces but the code doesn't; editing one usually means editing the other.

File AFile BSharedCoupling
internal/cache.go internal/server.go 22 34.4%
internal/server.go web/app.js 9 13.0%
README.md internal/server.go 6 8.1%

06 Authors · 3 contributors

Ownership measured by line-level git blame across the analysis window. Bus factor: 1; Alice owns the most code in window.

Author Code Files Owns In window Last commit
Alice <alice@example.com> 6,200 14 62.4% 64.0% 2026-01-14
Bob <bob@example.com> 2,400 8 24.1% 22.0% 2026-01-12
(before window) - - - - before window

07 Timeline · 4 buckets

Code lines by language over the analysed history window. Sparkline trajectory per language and per author.

LanguageStartNowΔTrajectory
Go 4,000 8,000 +4,000
JavaScript 2,200 2,400 +200
Markdown 200 240 +40

Author activity

AuthorCommitsΔ codeActivity
Alice 48 +3,800
Bob 22 +400

08 Cost estimate

Two ways to value the codebase: human-build effort (COCOMO, Boehm 1981) and machine-rebuild effort (LOCOMO, LLM regeneration model).

COCOMO : what it would have cost to write this from scratch with a team of developers

Effort
26.4
person-months · organic
Cost to develop
$297500
avg $56,286 · ×2.4 overhead
Schedule
8.4 mo
≈ 3.1 devs in parallel

LOCOMO : what it would cost to regenerate this with an LLM and review the output

Regen tokens
96.0K
output (in + out: 320K)
Regen time
30.0 min
at typical stream rate
Human review
12 hr
post-regeneration

09 Notable files

Per-file detail for the full tree (4 files). Sorted by lines descending; first ten shown, expand to see the rest.

FileLinesCodeCommentComplexityBytesULOC
internal/server.go 3,200 2,600 200 240 96,000 2,200
web/app.js 2,000 1,600 80 60 60,000 1,200
internal/cache.go 1,400 1,100 120 120 42,000 900
README.md 120 100 0 0 4,096 90