guardian/5-15-fun
File Size
The distribution of size of files (measured in lines of code).
File Size Overall
  • There are 3 files with 437 lines of code.
    • 0 very long files (0 lines of code)
    • 0 long files (0 lines of code)
    • 1 medium size files (203 lines of code)
    • 1 small files (158 lines of code)
    • 1 very small files (76 lines of code)
0% | 0% | 46% | 36% | 17%
Legend:
1001+
501-1000
201-500
101-200
1-100


explore: grouped by folders | grouped by size | sunburst | 3D view
File Size per Extension
1001+
501-1000
201-500
101-200
1-100
go0% | 0% | 46% | 36% | 17%
File Size per Logical Decomposition
primary
1001+
501-1000
201-500
101-200
1-100
ROOT0% | 0% | 46% | 36% | 17%
Longest Files (Top 3)
File# lines# units
main.go
in root
 203 5
suno.go
in root
 158 3
bedrock.go
in root
 76 2
Large Files That Change Often (Top 3)
To change a file, an AI coding agent (or a person) has to read it: these files are read the most for the changes in the past year (lines × changes).
File# lines≈ tokens
to read		# changes
(1y)		≈ lines edited
per change		lines read per
line changed
main.go
in root
 203 ~1k–3k 4 ~50 ~3
suno.go
in root
 158 ~1k–3k 3 ~50 ~3
bedrock.go
in root
 76 ~500–1.5k 2 ~2 ~30

Tokens are lines × 7 to 14 (analysis.fileReadsForChanges). Lines edited per change are the file's lines added and deleted divided by its commits over the whole history. Agents read about 2,000 lines at a time: when a 17,000-line file was split into modules, the tokens an agent read for the same change fell by 83% (The Economic Benefit of Refactoring, 2026).

Files With Most Units (Top 3)
File# lines# units
main.go
in root
 203 5
suno.go
in root
 158 3
bedrock.go
in root
 76 2
Files With Long Lines (Top 2)

There are 2 files with lines longer than 120 characters. In total, there are 8 long lines.

File# lines# units# long lines
main.go
in root
 203 5 6
suno.go
in root
 158 3 2
Correlations

File Size vs. Commits (all time): 3 points

suno.go x: 3 commits (all time) y: 158 lines of code main.go x: 4 commits (all time) y: 203 lines of code bedrock.go x: 2 commits (all time) y: 76 lines of code
203.0
lines of code
  min: 76.0
  average: 145.67
  25th percentile: 76.0
  median: 158.0
  75th percentile: 203.0
  max: 203.0
0 4.0
commits (all time)
min: 2.0 | average: 3.0 | 25th percentile: 2.0 | median: 3.0 | 75th percentile: 4.0 | max: 4.0

File Size vs. Contributors (all time): 3 points

suno.go x: 1 contributors (all time) y: 158 lines of code main.go x: 1 contributors (all time) y: 203 lines of code bedrock.go x: 1 contributors (all time) y: 76 lines of code
203.0
lines of code
  min: 76.0
  average: 145.67
  25th percentile: 76.0
  median: 158.0
  75th percentile: 203.0
  max: 203.0
0 1.0
contributors (all time)
min: 1.0 | average: 1.0 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 1.0 | max: 1.0

File Size vs. Commits (30 days): 0 points

No data for "commits (30d)" vs. "lines of code".

File Size vs. Contributors (30 days): 0 points

No data for "contributors (30d)" vs. "lines of code".

File Size vs. Commits (90 days): 0 points

No data for "commits (90d)" vs. "lines of code".

File Size vs. Contributors (90 days): 0 points

No data for "contributors (90d)" vs. "lines of code".

About This Analysis
  • File size measurements show the distribution of size of files.
  • Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
  • It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.
Learn more...