guardian/pluto-atomresponder
File Complexity*
The distribution of files by complexity: the sum of the McCabe indexes of their units.
File Complexity Overall
  • There are 29 files with units, with 1,633 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)
    • 1 slightly complex files (McCabe index sum 26-50; 261 lines of code)
    • 28 simple files (McCabe index sum 1-25; 1,372 lines of code)
  • 48 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system0% | 0% | 0% | 15% | 84%
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
py0% | 0% | 0% | 16% | 83%
go0% | 0% | 0% | 0% | 100%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
atomresponder0% | 0% | 0% | 34% | 65%
rabbitmq0% | 0% | 0% | 0% | 100%
kinesisresponder0% | 0% | 0% | 0% | 100%
test-sending-tool0% | 0% | 0% | 0% | 100%
ROOT0% | 0% | 0% | 0% | 100%
Most Complex Files (Top 29)

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
master_importer.py
in atomresponder
 261 11 47 18 16
kinesis_responder.py
in kinesisresponder
 128 7 25 20 15
atom_message.py
in atomresponder
 50 8 19 38 4
resync_cached_commissions.py
in rabbitmq/management/commands
 80 5 17 21 7
102 3 17 17 11
s3_mixin.py
in atomresponder
 81 8 17 21 6
58 5 15 26 4
61 4 13 21 6
25 4 11 44 6
vs_mixin.py
in atomresponder
 54 3 11 20 7
kinesis_responder_basecommand.py
in kinesisresponder/management
 42 2 10 24 9
83 2 8 10 5
run_rabbitmq_responder.py
in rabbitmq/management/commands
 78 6 8 10 3
views.py
in atomresponder
 48 3 8 17 4
models.py
in atomresponder
 50 3 7 14 4
message_schema.py
in atomresponder
 70 1 7 10 7
main.go
in test-sending-tool
 45 2 6 13 3
media_atom.py
in atomresponder
 49 4 6 12 2
request_atom_resync.py
in atomresponder/management/commands
 15 2 6 40 5
run_atom_responder.py
in atomresponder/management/commands
 37 2 6 16 5
pac_xml.py
in atomresponder
 31 2 6 19 3
sentry.py
in kinesisresponder
 26 2 6 23 3
19 1 5 26 5
fix_broken_proxy.py
in atomresponder/management/commands
 21 1 4 19 4
manage.py
in root
 15 1 2 13 2
show_kinesis_stream.py
in kinesisresponder/management/commands
 22 2 2 9 1
models.py
in rabbitmq
 21 1 1 5 1
media_atom.py
in rabbitmq
 45 1 1 2 1
views.py
in kinesisresponder
 16 1 1 6 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...