• There are 6 files with units, with 509 lines of code.
• 0 very complex files (McCabe index sum 251+; 0 lines of code)
• 0 complex files (McCabe index sum 126-250; 0 lines of code)
• 0 medium complex files (McCabe index sum 51-125; 0 lines of code)
• 0 slightly complex files (McCabe index sum 26-50; 0 lines of code)
• 6 simple files (McCabe index sum 1-25; 509 lines of code)
• 17 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.

The McCabe index of a file grows with its size: per 100 lines tells a large but plain file from a dense one, and most complex unit whether the complexity sits in one unit or is spread over many.

File	# lines	# units	McCabe index (sum)	per 100 lines	most complex unit
app.js in src/js	188	9	18	10	6
gulpfile.babel.js in root	261	6	9	3	2
main.js in src/js	25	2	4	16	3
process.py in processing	22	1	1	5	1
render.js in src	4	1	1	25	1
index.js in src/components/load-json	9	1	1	11	1

• File complexity is the sum of the McCabe indexes (conditional complexity) of the units (methods, functions...) in a file.
• Files are classified in five categories based on that sum: 1-25 (simple files), 26-50 (slightly complex files), 51-125 (medium complex files), 126-250 (complex files), 251+ (very complex files). The default bands are five times the unit complexity bands, as a file is a group of units.
• Only main code files with units are classified. Files without units (languages without unit analysis, or files without functions) have no complexity to measure and are left out rather than counted as simple.
• A very complex file holds many decisions, which often means it has too many responsibilities: a candidate to split, and a place where changes need more testing.