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

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
Fetching.scala in core/src/main/scala/com/gu/etagcaching/fetching	76	~500–1.5k	2	~30	~3
Loading.scala in core/src/main/scala/com/gu/etagcaching	27	under 1k	3	~20	~2
S3ObjectFetching.scala in aws-s3/aws-sdk-v2/src/main/scala/com/gu/etagcaching/aws/sdkv2/s3	43	under 1k	1	~15	~3
ETagCache.scala in core/src/main/scala/com/gu/etagcaching	20	under 1k	1	~15	~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).

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

File	# lines	# units	# long lines
Fetching.scala in core/src/main/scala/com/gu/etagcaching/fetching	76	5	5
ETagCache.scala in core/src/main/scala/com/gu/etagcaching	20	-	1
Loading.scala in core/src/main/scala/com/gu/etagcaching	27	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.