File Complexity Overall
  • There are 35 files with units, with 2,655 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)
    • 3 slightly complex files (McCabe index sum 26-50; 477 lines of code)
    • 32 simple files (McCabe index sum 1-25; 2,178 lines of code)
  • 3 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system0% | 0% | 0% | 17% | 82%
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
go0% | 0% | 0% | 17% | 82%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
test-suites0% | 0% | 0% | 17% | 82%
Most Complex Files (Top 35)

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
provider.go
in test-suites/nameconstraints
225 8 31 14 18
cert_util.go
in test-suites/certutil
134 6 29 22 18
summary.go
in test-suites/cmd/bettertls
118 2 27 23 20
provider.go
in test-suites/pathbuilding
123 8 24 20 8
server.go
in test-suites/test-executor
199 4 24 12 20
trust_graph.go
in test-suites/pathbuilding
149 9 21 14 7
common.go
in test-suites/impltests
88 5 17 19 7
int_set.go
in test-suites/int-set
70 5 17 24 6
generate_certs.go
in test-suites/pathbuilding
95 1 16 17 16
get_manifest.go
in test-suites/cmd/bettertls
86 3 15 17 6
envoy.go
in test-suites/impltests
132 5 15 11 10
pkijs.go
in test-suites/impltests
113 5 14 12 6
powershell.go
in test-suites/impltests
102 5 14 14 9
show_results.go
in test-suites/cmd/bettertls
64 1 12 19 12
suites.go
in test-suites/test-executor
53 6 10 19 3
java.go
in test-suites/impltests
96 5 10 10 5
python_requests.go
in test-suites/impltests
56 5 9 16 4
rustls.go
in test-suites/impltests
51 5 9 18 4
node.go
in test-suites/impltests
68 5 9 13 4
get_test_command.go
in test-suites/cmd/bettertls
53 1 7 13 7
run_server.go
in test-suites/cmd/bettertls
52 1 7 13 7
util_go1.18.go
in test-suites/test-executor
23 1 7 30 7
libressl.go
in test-suites/impltests
46 5 7 15 3
openssl.go
in test-suites/impltests
41 5 7 17 2
golang.go
in test-suites/impltests
45 5 7 16 3
main.go
in test-suites/cmd/bettertls
34 1 6 18 6
string_set.go
in test-suites/pathbuilding
24 5 6 25 2
curl.go
in test-suites/impltests
33 5 6 18 2
botan.go
in test-suites/impltests
35 5 6 17 2
gnutls.go
in test-suites/impltests
33 5 6 18 2
explicit_test_cases.go
in test-suites/pathbuilding
155 3 5 3 3
boringssl.go
in test-suites/impltests
26 5 5 19 1
x509.go
in test-suites/nameconstraints
22 1 2 9 2
nop_logger.go
in test-suites/test-executor
7 1 1 14 1
util_older.go
in test-suites/test-executor
4 1 1 25 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...