File Complexity Overall
  • There are 69 files with units, with 4,128 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; 217 lines of code)
    • 4 slightly complex files (McCabe index sum 26-50; 627 lines of code)
    • 64 simple files (McCabe index sum 1-25; 3,284 lines of code)
  • 7 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system0% | 0% | 5% | 15% | 79%
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% | 5% | 15% | 79%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
internal0% | 0% | 5% | 15% | 79%
cmd0% | 0% | 0% | 0% | 100%
Most Complex Files (Top 50)

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
remote.go
in internal/storage/remote
217 11 58 27 15
temporary.go
in internal/storage/temporary
147 5 39 27 17
local.go
in internal/storage/local
112 7 27 24 7
run.go
in internal/command/run
161 2 27 17 26
push.go
in internal/oci
207 5 26 13 12
gvisor.go
in internal/network/software/gvisor
177 7 23 13 7
vmdirectory.go
in internal/vmdirectory
99 12 22 22 4
list.go
in internal/command/list
126 3 20 16 15
set.go
in internal/command/set
99 3 19 19 11
applestream.go
in internal/oci/pull/tart/applestream
99 3 18 18 13
clone.go
in internal/command/clone
92 2 18 20 17
host.go
in internal/network/host
92 4 17 18 11
software.go
in internal/network/software
105 4 17 16 14
diskpuller.go
in internal/oci/diskpuller
125 2 17 14 13
firmware.go
in internal/externalbinary/firmware
87 3 16 18 7
pull.go
in internal/storage/remote
81 1 16 20 16
vetu.go
in internal/oci/pull/vetu
103 1 15 15 15
login.go
in internal/command/login
93 3 15 16 8
binaryfetcher.go
in internal/binaryfetcher
60 2 14 23 11
simplename.go
in internal/name/simplename
34 1 14 41 14
chunker.go
in internal/chunker
91 5 14 15 5
create.go
in internal/command/create
93 2 13 14 12
filelock.go
in internal/filelock
59 6 12 20 4
push.go
in internal/command/push
76 2 12 16 11
ip.go
in internal/command/ip
84 3 12 14 7
remotename.go
in internal/name/remotename
55 2 12 22 9
pidlock.go
in internal/pidlock
52 6 11 21 4
subnetfinder.go
in internal/network/subnetfinder
58 1 10 17 10
dhcp.go
in internal/network/software/dhcp
80 3 10 13 5
stop.go
in internal/command/stop
71 2 10 14 9
bridged.go
in internal/network/bridged
45 4 9 20 6
tart.go
in internal/oci/pull/tart
85 1 9 11 9
dhcp.go
in internal/network/host
62 3 8 13 5
fetchurl.go
in internal/binaryfetcher
38 2 8 21 4
main.go
in cmd/vetu
55 1 7 13 7
vmconfig.go
in internal/vmconfig
48 2 7 15 6
sparseio.go
in internal/sparseio
29 1 7 24 7
delete.go
in internal/command/delete
45 2 7 16 6
explicitlypulled.go
in internal/vmdirectory
26 3 7 27 5
globallock.go
in internal/globallock
28 1 6 21 6
cloudhypervisor.go
in internal/externalcommand/cloudhypervisor
42 1 6 14 6
fqn.go
in internal/command/fqn
40 2 6 15 5
afpacket.go
in internal/afpacket
30 2 6 20 5
tap.go
in internal/tuntap
24 1 5 21 5
host_unsupported.go
in internal/network/host
20 4 4 20 1
software_unsupported.go
in internal/network/software
20 4 4 20 1
bridged_unsupported.go
in internal/network/bridged
19 4 4 21 1
pull.go
in internal/oci
38 1 4 11 4
tartconfig.go
in internal/oci/pull/tart/tartconfig
31 1 4 13 4
version.go
in internal/version
23 1 4 17 4
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...