openai/openai-structured-outputs-samples
File Size The distribution of size of files (measured in lines of code). |
File Size Overall
- There are 67 files with 4,650 lines of code.
- 0 very long files (0 lines of code)
- 0 long files (0 lines of code)
- 5 medium size files (1,391 lines of code)
- 6 small files (829 lines of code)
- 56 very small files (2,430 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 50)
| File | # lines | # units |
|---|---|---|
| 338 | - | |
| 311 | 1 | |
| 311 | 1 | |
| 226 | - | |
| 205 | 1 | |
| 163 | - | |
| 154 | - | |
| 139 | 2 | |
| 135 | - | |
| 121 | - | |
| 117 | 3 | |
| 100 | - | |
| 100 | - | |
| 99 | 1 | |
| 97 | - | |
| 97 | - | |
| 96 | 5 | |
| 93 | - | |
| 91 | 3 | |
| 89 | - | |
| 89 | - | |
| 89 | - | |
| 87 | - | |
| 77 | - | |
| 76 | - | |
| 76 | - | |
| 72 | - | |
| 65 | - | |
| 64 | - | |
| 63 | - | |
| 62 | - | |
| 46 | - | |
| 43 | - | |
| 43 | - | |
| 41 | - | |
| 41 | - | |
| 35 | 1 | |
| 35 | 1 | |
| 35 | 1 | |
| 35 | 1 | |
| 33 | - | |
| 33 | - | |
| 33 | - | |
| 29 | - | |
| 27 | - | |
| 24 | - | |
| 24 | - | |
| 20 | 2 | |
| 20 | - | |
| 16 | 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 |
|---|---|---|---|---|---|
| 24 | under 1k | 2 | ~2 | ~10 | |
| 20 | under 1k | 2 | ~2 | ~10 |
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 18)
| File | # lines | # units |
|---|---|---|
| 96 | 5 | |
| 91 | 3 | |
| 117 | 3 | |
| 20 | 2 | |
| 139 | 2 | |
| 35 | 1 | |
| 13 | 1 | |
| 16 | 1 | |
| 13 | 1 | |
| 311 | 1 | |
| 35 | 1 | |
| 5 | 1 | |
| 205 | 1 | |
| 35 | 1 | |
| 99 | 1 | |
| 311 | 1 | |
| 5 | 1 | |
| 35 | 1 |
Files With Long Lines (Top 13)
There are 13 files with lines longer than 120 characters. In total, there are 29 long lines.
| File | # lines | # units | # long lines |
|---|---|---|---|
| 24 | - | 5 | |
| 20 | - | 5 | |
| 139 | 2 | 4 | |
| 97 | - | 3 | |
| 226 | - | 2 | |
| 311 | 1 | 2 | |
| 311 | 1 | 2 | |
| 100 | - | 1 | |
| 46 | - | 1 | |
| 99 | 1 | 1 | |
| 100 | - | 1 | |
| 77 | - | 1 | |
| 64 | - | 1 |
Correlations
File Size vs. Commits (all time): 6 points
|
|
226.0 | lines of code min: 20.0average: 80.17 25th percentile: 23.0 median: 56.0 75th percentile: 130.75 max: 226.0 |
|
| 0 | 2.0 | ||
|
commits (all time) min: 1.0 | average: 1.33 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 2.0 | max: 2.0
|
|||
File Size vs. Contributors (all time): 6 points
|
|
226.0 | lines of code min: 20.0average: 80.17 25th percentile: 23.0 median: 56.0 75th percentile: 130.75 max: 226.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