File Size Overall
- There are 13 files with 1,877 lines of code.
- 0 very long files (0 lines of code)
- 0 long files (0 lines of code)
- 6 medium size files (1,568 lines of code)
- 2 small files (250 lines of code)
- 5 very small files (59 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 13)
| File | # lines | # units |
|---|---|---|
| 353 | 22 | |
| 320 | 19 | |
| 260 | 14 | |
| 215 | 7 | |
| 210 | 5 | |
| 210 | 6 | |
| 135 | 3 | |
| 115 | 4 | |
| 30 | 2 | |
| 15 | - | |
| 12 | - | |
| 1 | - | |
| 1 | - |
Large Files That Change Often (Top 2)
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 |
|---|---|---|---|---|---|
| 15 | under 1k | 1 | ~7 | ~2 | |
| 12 | under 1k | 1 | ~3 | ~3 |
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 9)
| File | # lines | # units |
|---|---|---|
| 353 | 22 | |
| 320 | 19 | |
| 260 | 14 | |
| 215 | 7 | |
| 210 | 6 | |
| 210 | 5 | |
| 115 | 4 | |
| 135 | 3 | |
| 30 | 2 |
Files With Long Lines (Top 8)
There are 8 files with lines longer than 120 characters. In total, there are 14 long lines.
| File | # lines | # units | # long lines |
|---|---|---|---|
| 215 | 7 | 3 | |
| 12 | - | 2 | |
| 210 | 5 | 2 | |
| 115 | 4 | 2 | |
| 260 | 14 | 2 | |
| 320 | 19 | 1 | |
| 135 | 3 | 1 | |
| 353 | 22 | 1 |
Correlations
File Size vs. Commits (all time): 2 points
|
|
15.0 | lines of code min: 12.0average: 13.5 25th percentile: 12.0 median: 13.5 75th percentile: 15.0 max: 15.0 |
|
| 0 | 1.0 | ||
|
commits (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. Contributors (all time): 2 points
|
|
15.0 | lines of code min: 12.0average: 13.5 25th percentile: 12.0 median: 13.5 75th percentile: 15.0 max: 15.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...
- 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