Netflix/x-test
File Size
The distribution of size of files (measured in lines of code).
File Size Overall
  • There are 4 files with 532 lines of code.
    • 0 very long files (0 lines of code)
    • 0 long files (0 lines of code)
    • 1 medium size files (385 lines of code)
    • 0 small files (0 lines of code)
    • 3 very small files (147 lines of code)
0% | 0% | 72% | 0% | 27%
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
js0% | 0% | 72% | 0% | 27%
File Size per Logical Decomposition
primary
1001+
501-1000
201-500
101-200
1-100
ROOT0% | 0% | 72% | 0% | 27%
Longest Files (Top 4)
File# lines# units
x-test.js
in root
 385 9
server.js
in root
 92 6
40 -
15 -
Large Files That Change Often (Top 3)
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
x-test.js
in root
 385 ~2k–7k 16 ~150 ~2
15 under 1k 7 ~5 ~3
40 under 1k 2 ~30 ~2

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
x-test.js
in root
 385 9
server.js
in root
 92 6
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): 4 points

x-test.js x: 28 commits (all time) y: 385 lines of code x-test.config.js x: 7 commits (all time) y: 15 lines of code eslint.config.js x: 5 commits (all time) y: 40 lines of code server.js x: 4 commits (all time) y: 92 lines of code
385.0
lines of code
  min: 15.0
  average: 133.0
  25th percentile: 21.25
  median: 66.0
  75th percentile: 311.75
  max: 385.0
0 28.0
commits (all time)
min: 4.0 | average: 11.0 | 25th percentile: 4.25 | median: 6.0 | 75th percentile: 22.75 | max: 28.0

File Size vs. Contributors (all time): 4 points

x-test.js x: 1 contributors (all time) y: 385 lines of code x-test.config.js x: 1 contributors (all time) y: 15 lines of code eslint.config.js x: 1 contributors (all time) y: 40 lines of code server.js x: 1 contributors (all time) y: 92 lines of code
385.0
lines of code
  min: 15.0
  average: 133.0
  25th percentile: 21.25
  median: 66.0
  75th percentile: 311.75
  max: 385.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...