guardian/guardian-engineering-site
File Size The distribution of size of files (measured in lines of code). |
File Size Overall
- There are 9 files with 684 lines of code.
- 0 very long files (0 lines of code)
- 0 long files (0 lines of code)
- 1 medium size files (368 lines of code)
- 1 small files (130 lines of code)
- 7 very small files (186 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 9)
| File | # lines | # units |
|---|---|---|
| 368 | 22 | |
| 130 | - | |
| 65 | - | |
| 48 | - | |
| 29 | 1 | |
| 19 | - | |
| 11 | - | |
| 11 | - | |
| 3 | - |
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 |
|---|---|---|---|---|---|
| 130 | ~700–2k | 2 | ~50 | ~3 | |
| 19 | under 1k | 2 | ~5 | ~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 2)
| File | # lines | # units |
|---|---|---|
| 368 | 22 | |
| 29 | 1 |
Files With Long Lines (Top 3)
There are 3 files with lines longer than 120 characters. In total, there are 18 long lines.
| File | # lines | # units | # long lines |
|---|---|---|---|
| 368 | 22 | 16 | |
| 11 | - | 1 | |
| 29 | 1 | 1 |
Correlations
File Size vs. Commits (all time): 9 points
|
|
368.0 | lines of code min: 3.0average: 76.0 25th percentile: 11.0 median: 29.0 75th percentile: 97.5 max: 368.0 |
|
| 0 | 23.0 | ||
|
commits (all time) min: 2.0 | average: 6.78 | 25th percentile: 2.5 | median: 5.0 | 75th percentile: 9.0 | max: 23.0
|
|||
File Size vs. Contributors (all time): 9 points
|
|
368.0 | lines of code min: 3.0average: 76.0 25th percentile: 11.0 median: 29.0 75th percentile: 97.5 max: 368.0 |
|
| 0 | 6.0 | ||
|
contributors (all time) min: 1.0 | average: 1.78 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 2.0 | max: 6.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