• There are 8 files with 523 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)
• 3 small files (394 lines of code)
• 5 very small files (129 lines of code)

File	# lines	≈ tokens to read	# changes (1y)	≈ lines edited per change	lines read per line changed
main.py in gateway	183	~1k–3k	4	~30	~7
jwks.py in gateway	108	~700–2k	4	~15	~7
mapping.py in gateway	103	~700–1.5k	4	~30	~3
auth.py in gateway	82	~500–1.5k	4	~30	~2
config.example.yaml in root	14	under 1k	7	~15	~1
constants.py in gateway	9	under 1k	8	~10	~1
access_log.py in gateway	22	under 1k	3	~30	~1
__init__.py in gateway	2	under 1k	2	~2	~1

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 0 files with lines longer than 120 characters. In total, there are 0 long lines.

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