• There are 42 files with units, with 9,925 lines of code.
• 0 very complex files (McCabe index sum 251+; 0 lines of code)
• 1 complex files (McCabe index sum 126-250; 1,338 lines of code)
• 10 medium complex files (McCabe index sum 51-125; 5,196 lines of code)
• 6 slightly complex files (McCabe index sum 26-50; 1,024 lines of code)
• 25 simple files (McCabe index sum 1-25; 2,367 lines of code)
• 24 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
urls.py in src/guardrails/checks/text	1338	45	219	16	32
secret_keys.py in src/guardrails/checks/text	503	16	105	21	41
review_state.py in .agents/skills/implementation-final-review/scripts	650	31	103	16	13
pii.py in src/guardrails/checks/text	427	13	99	23	30
review_protocol.py in .agents/skills/implementation-final-review/scripts	1289	28	91	7	12
_base_client.py in src/guardrails	265	26	76	29	14
conversation.py in src/guardrails/utils	219	13	75	34	12
client.py in src/guardrails	551	27	60	11	11
agents.py in src/guardrails	413	14	59	14	19
guardrail_evals.py in src/guardrails/evals	627	11	57	9	10
validate_handoff.py in .agents/skills/implementation-kickoff/scripts	252	9	53	21	23
visualizer.py in src/guardrails/evals/core	212	10	42	20	7
benchmark_calculator.py in src/guardrails/evals/core	92	7	29	32	7
async_engine.py in src/guardrails/evals/core	279	7	28	10	12
prompt_injection_detection.py in src/guardrails/checks/text	208	6	28	13	16
types.py in src/guardrails	140	7	28	20	11
output.py in src/guardrails/utils	93	9	26	28	8
llm_base.py in src/guardrails/checks/text	333	9	22	7	9
benchmark_reporter.py in src/guardrails/evals/core	154	9	21	14	7
calculator.py in src/guardrails/evals/core	41	2	20	49	17
parsing.py in src/guardrails/utils	147	9	20	14	5
registry.py in src/guardrails	100	8	18	18	5
keywords.py in src/guardrails/checks/text	72	3	17	24	13
runtime.py in src/guardrails	207	10	15	7	3
responses.py in src/guardrails/resources/responses	265	5	13	5	8
schema.py in src/guardrails/utils	149	7	13	9	3
chat.py in src/guardrails/resources/chat	119	7	12	10	6
validate_dataset.py in src/guardrails/evals/core	55	2	11	20	7
cli.py in src/guardrails	53	2	8	15	7
jsonl_loader.py in src/guardrails/evals/core	34	1	7	21	7
json_reporter.py in src/guardrails/evals/core	87	4	7	8	3
anonymizer.py in src/guardrails/utils	51	2	7	14	6
context.py in src/guardrails	23	5	5	22	1
exceptions.py in src/guardrails	27	5	5	19	1
types.py in src/guardrails/evals/core	51	4	4	8	1
latency_tester.py in src/guardrails/evals/core	62	3	4	6	2
__init__.py in src/guardrails/evals	32	1	2	6	2
moderation.py in src/guardrails/checks/text	101	2	2	2	1
spec.py in src/guardrails	40	2	2	5	1
context.py in src/guardrails/utils	38	2	2	5	1
safety_identifier.py in src/guardrails/utils	24	1	1	4	1
_streaming.py in src/guardrails	102	1	1	1	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.