openai/LongGapsBetweenPrimes
File Size
The distribution of size of files (measured in lines of code).
File Size Overall
  • There are 4 files with 4,342 lines of code.
    • 1 very long files (4,217 lines of code)
    • 0 long files (0 lines of code)
    • 0 medium size files (0 lines of code)
    • 0 small files (0 lines of code)
    • 3 very small files (125 lines of code)
97% | 0% | 0% | 0% | 2%
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
lean99% | 0% | 0% | 0% | <1%
yaml0% | 0% | 0% | 0% | 100%
toml0% | 0% | 0% | 0% | 100%
File Size per Logical Decomposition
primary
1001+
501-1000
201-500
101-200
1-100
ROOT97% | 0% | 0% | 0% | 2%
Longest Files (Top 4)
File# lines# units
4217 -
88 -
25 -
lean
 12 -
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
88 ~500–1.5k 1 ~1 ~100

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 0)
File# lines# units
Files With Long Lines (Top 0)

There are 0 files with lines longer than 120 characters. In total, there are 0 long lines.

File# lines# units# long lines
Correlations

File Size vs. Commits (all time): 1 points

formalization.yaml x: 1 commits (all time) y: 88 lines of code
88.0
lines of code
  min: 88.0
  average: 88.0
  25th percentile: 88.0
  median: 88.0
  75th percentile: 88.0
  max: 88.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): 1 points

formalization.yaml x: 1 contributors (all time) y: 88 lines of code
88.0
lines of code
  min: 88.0
  average: 88.0
  25th percentile: 88.0
  median: 88.0
  75th percentile: 88.0
  max: 88.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): 1 points

formalization.yaml x: 1 commits (90d) y: 88 lines of code
88.0
lines of code
  min: 88.0
  average: 88.0
  25th percentile: 88.0
  median: 88.0
  75th percentile: 88.0
  max: 88.0
0 1.0
commits (90d)
min: 1.0 | average: 1.0 | 25th percentile: 1.0 | median: 1.0 | 75th percentile: 1.0 | max: 1.0

File Size vs. Contributors (90 days): 1 points

formalization.yaml x: 1 contributors (90d) y: 88 lines of code
88.0
lines of code
  min: 88.0
  average: 88.0
  25th percentile: 88.0
  median: 88.0
  75th percentile: 88.0
  max: 88.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...