File Size Overall
- There are 16 files with 2,151 lines of code.
- 0 very long files (0 lines of code)
- 2 long files (1,313 lines of code)
- 2 medium size files (541 lines of code)
- 0 small files (0 lines of code)
- 12 very small files (297 lines of code)
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
File Size per Logical Decomposition
primary
Longest Files (Top 16)
| File | # lines | # units |
|---|---|---|
| 741 | - | |
| 572 | - | |
| 329 | 16 | |
| 212 | 1 | |
| 51 | 1 | |
| 50 | 5 | |
| 34 | - | |
| 31 | - | |
| 30 | - | |
| 28 | - | |
| 27 | - | |
| 17 | - | |
| 8 | - | |
| 8 | - | |
| 8 | - | |
| 5 | 1 |
Large Files That Change Often (Top 4)
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 |
|---|---|---|---|---|---|
| 741 | ~5k–15k | 4 | ~70 | ~10 | |
| 572 | ~3k–10k | 2 | ~50 | ~10 | |
| 212 | ~1k–3k | 4 | ~15 | ~15 | |
| 329 | ~2k–5k | 2 | ~50 | ~7 |
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 5)
| File | # lines | # units |
|---|---|---|
| 329 | 16 | |
| 50 | 5 | |
| 212 | 1 | |
| 51 | 1 | |
| 5 | 1 |
Files With Long Lines (Top 2)
There are 2 files with lines longer than 120 characters. In total, there are 2 long lines.
| File | # lines | # units | # long lines |
|---|---|---|---|
| 212 | 1 | 1 | |
| 329 | 16 | 1 |
Correlations
File Size vs. Commits (all time): 16 points
|
|
741.0 | lines of code min: 5.0average: 134.44 25th percentile: 10.25 median: 30.5 75th percentile: 171.75 max: 741.0 |
|
| 0 | 55.0 | ||
|
commits (all time) min: 2.0 | average: 17.63 | 25th percentile: 6.75 | median: 10.5 | 75th percentile: 25.25 | max: 55.0
|
|||
File Size vs. Contributors (all time): 16 points
|
|
741.0 | lines of code min: 5.0average: 134.44 25th percentile: 10.25 median: 30.5 75th percentile: 171.75 max: 741.0 |
|
| 0 | 5.0 | ||
|
contributors (all time) min: 2.0 | average: 2.94 | 25th percentile: 2.0 | median: 3.0 | 75th percentile: 3.0 | max: 5.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...
- To learn more about bloaters and how to deal with long code structures, Sokrates recommends the following resources:
- Refactoring bloaters, sourcemaking.com
- The Blob Software Development Anti-Pattern, sourcemaking.com