File Complexity Overall
  • There are 10 files with units, with 1,336 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)
    • 1 medium complex files (McCabe index sum 51-125; 302 lines of code)
    • 0 slightly complex files (McCabe index sum 26-50; 0 lines of code)
    • 9 simple files (McCabe index sum 1-25; 1,034 lines of code)
  • 9 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system0% | 0% | 22% | 0% | 77%
Legend:
251+
126-250
51-125
26-50
1-25


explore: grouped by folders | grouped by complexity
File Complexity per Extension
251+
126-250
51-125
26-50
1-25
ts0% | 0% | 22% | 0% | 77%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
src0% | 0% | 27% | 0% | 72%
cdk0% | 0% | 0% | 0% | 100%
Most Complex Files (Top 10)

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# unitsMcCabe index
(sum)
per 100
lines
most complex
unit
transforms.ts
in src/libs
302 23 52 17 13
zuora.ts
in src/libs
282 10 17 6 3
salesforce.ts
in src/libs
130 5 12 9 7
main.ts
in src
145 5 7 5 2
identity.ts
in src/libs
60 3 7 12 5
cloudwatch.ts
in src/utils
61 2 6 10 3
s3.ts
in src/libs
42 4 5 12 2
245 1 2 1 2
ssm.ts
in src/utils
15 1 1 7 1
local.ts
in src
54 1 1 2 1
About This Analysis
  • 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.
Learn more...