• There are 15 files with 365 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)
• 0 small files (0 lines of code)
• 15 very small files (365 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
Lambda.scala in src/main/scala/ophan/google/index/checker	74	~500–1.5k	2	~15	~5
GoogleSearchService.scala in src/main/scala/ophan/google/index/checker	69	~300–1k	2	~30	~2
ContentSummary.scala in src/main/scala/ophan/google/index/checker/model	32	under 1k	2	~10	~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).

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

File	# lines	# units	# long lines
Lambda.scala in src/main/scala/ophan/google/index/checker	74	4	2
ContentSummary.scala in src/main/scala/ophan/google/index/checker/model	32	2	2
ContentAvailabilityInGoogleIndex.scala in src/main/scala/ophan/google/index/checker/model	13	1	1
GoogleSearchService.scala in src/main/scala/ophan/google/index/checker	69	2	1

• 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.