guardian/image-url-signing-service
File Size The distribution of size of files (measured in lines of code). |
File Size Overall
- There are 9 files with 695 lines of code.
- 0 very long files (0 lines of code)
- 0 long files (0 lines of code)
- 1 medium size files (214 lines of code)
- 2 small files (335 lines of code)
- 6 very small files (146 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 |
|---|---|---|
| 214 | 6 | |
| 191 | - | |
| 144 | 2 | |
| 63 | 5 | |
| 28 | 1 | |
| 18 | - | |
| 18 | - | |
| 15 | - | |
| 4 | - |
Large Files That Change Often (Top 7)
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 |
|---|---|---|---|---|---|
| 191 | ~1k–3k | 4 | ~15 | ~10 | |
| 214 | ~1k–3k | 2 | ~30 | ~7 | |
| 63 | ~300–1k | 5 | ~10 | ~5 | |
| 144 | ~1k–3k | 2 | ~30 | ~5 | |
| 18 | under 1k | 4 | ~10 | ~2 | |
| 28 | under 1k | 2 | ~30 | ~1 | |
| 15 | under 1k | 2 | ~15 | ~1 |
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 4)
| File | # lines | # units |
|---|---|---|
| 214 | 6 | |
| 63 | 5 | |
| 144 | 2 | |
| 28 | 1 |
Files With Long Lines (Top 2)
Correlations
File Size vs. Commits (all time): 9 points
|
|
214.0 | lines of code min: 4.0average: 77.22 25th percentile: 16.5 median: 28.0 75th percentile: 167.5 max: 214.0 |
|
| 0 | 26.0 | ||
|
commits (all time) min: 2.0 | average: 12.67 | 25th percentile: 5.5 | median: 8.0 | 75th percentile: 22.5 | max: 26.0
|
|||
File Size vs. Contributors (all time): 9 points
|
|
214.0 | lines of code min: 4.0average: 77.22 25th percentile: 16.5 median: 28.0 75th percentile: 167.5 max: 214.0 |
|
| 0 | 10.0 | ||
|
contributors (all time) min: 2.0 | average: 5.56 | 25th percentile: 3.0 | median: 5.0 | 75th percentile: 7.5 | max: 10.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