• There are 9 files with units, with 4,308 lines of code.
• 0 very complex files (McCabe index sum 251+; 0 lines of code)
• 3 complex files (McCabe index sum 126-250; 3,227 lines of code)
• 1 medium complex files (McCabe index sum 51-125; 697 lines of code)
• 0 slightly complex files (McCabe index sum 26-50; 0 lines of code)
• 5 simple files (McCabe index sum 1-25; 384 lines of code)
• 3 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
_azure.py in blobfile	1265	54	236	19	35
_context.py in blobfile	1207	53	217	18	28
_common.py in blobfile	755	58	174	23	19
_gcp.py in blobfile	697	49	124	18	7
_ops.py in blobfile	175	23	23	13	1
_xml.py in blobfile	55	4	17	31	10
performance_test_parallel.py in scripts	65	3	10	15	6
run.py in testing	77	3	8	10	4
conftest.py in root	12	3	6	50	4

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