guardian/cq-source-image-packages
File Size The distribution of size of files (measured in lines of code). |
File Size Overall
- There are 10 files with 463 lines of code.
- 0 very long files (0 lines of code)
- 0 long files (0 lines of code)
- 0 medium size files (0 lines of code)
- 1 small files (181 lines of code)
- 9 very small files (282 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 10)
| File | # lines | # units |
|---|---|---|
| 181 | 9 | |
| 74 | 5 | |
| 47 | 3 | |
| 39 | 2 | |
| 34 | - | |
| 30 | 2 | |
| 26 | - | |
| 13 | 1 | |
| 12 | 1 | |
| 7 | - |
Large Files That Change Often (Top 1)
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 |
|---|---|---|---|---|---|
| 26 | under 1k | 5 | ~7 | ~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 7)
Files With Long Lines (Top 2)
Correlations
File Size vs. Commits (all time): 10 points
|
|
181.0 | lines of code min: 7.0average: 46.3 25th percentile: 12.75 median: 32.0 75th percentile: 53.75 max: 181.0 |
|
| 0 | 6.0 | ||
|
commits (all time) min: 1.0 | average: 2.2 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 3.25 | max: 6.0
|
|||
File Size vs. Contributors (all time): 10 points
|
|
181.0 | lines of code min: 7.0average: 46.3 25th percentile: 12.75 median: 32.0 75th percentile: 53.75 max: 181.0 |
|
| 0 | 4.0 | ||
|
contributors (all time) min: 1.0 | average: 1.6 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 2.25 | max: 4.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): 1 points
|
|
26.0 | lines of code min: 26.0average: 26.0 25th percentile: 26.0 median: 26.0 75th percentile: 26.0 max: 26.0 |
|
| 0 | 4.0 | ||
|
commits (90d) min: 4.0 | average: 4.0 | 25th percentile: 4.0 | median: 4.0 | 75th percentile: 4.0 | max: 4.0
|
|||
File Size vs. Contributors (90 days): 1 points
|
|
26.0 | lines of code min: 26.0average: 26.0 25th percentile: 26.0 median: 26.0 75th percentile: 26.0 max: 26.0 |
|
| 0 | 1.0 | ||
|
contributors (90d) min: 1.0 | average: 1.0 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 1.0 | max: 1.0
|
|||
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