Netflix/falcor
File Complexity*
The distribution of files by complexity: the sum of the McCabe indexes of their units.
File Complexity Overall
  • There are 58 files with units, with 10,619 lines of code.
    • 1 very complex files (McCabe index sum 251+; 6,272 lines of code)
    • 0 complex files (McCabe index sum 126-250; 0 lines of code)
    • 1 medium complex files (McCabe index sum 51-125; 443 lines of code)
    • 3 slightly complex files (McCabe index sum 26-50; 683 lines of code)
    • 53 simple files (McCabe index sum 1-25; 3,221 lines of code)
  • 151 main files have no units (e.g. languages without unit analysis, or files without functions) and are not classified.
system59% | 0% | 4% | 6% | 30%
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
js59% | 0% | 4% | 6% | 30%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
performance84% | 0% | 0% | 0% | 15%
build0% | 0% | 75% | 0% | 24%
lib0% | 0% | 0% | 26% | 73%
ROOT0% | 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
_.js
in performance/models/legacy
 6272 93 2713 43 868
publish.js
in build/falcor-jsdoc-template
 443 33 118 27 20
Model.js
in lib
 325 4 35 11 32
GetRequestV2.js
in lib/request
 170 6 32 19 15
setPathMaps.js
in lib/set
 188 4 30 16 8
invalidatePathMaps.js
in lib/invalidate
 116 3 25 22 10
RequestQueueV2.js
in lib/request
 103 6 24 23 13
CSVTransform.js
in performance/formatter
 101 8 24 24 9
invalidatePathSets.js
in lib/invalidate
 122 3 20 16 8
complement.js
in lib/request
 125 5 20 16 9
168 3 20 12 8
187 3 18 10 8
testRunner.js
in performance
 71 8 18 25 4
69 1 17 25 17
57 4 15 26 9
get.js
in lib/get
 73 2 13 18 11
ModelResponse.js
in lib/response
 79 7 12 15 3
getCache.js
in lib/get
 47 4 12 26 6
setRequestCycle.js
in lib/response/set
 80 4 10 13 7
34 7 10 29 2
onMissing.js
in lib/get
 49 2 9 18 8
83 6 9 11 4
getRequestCycle.js
in lib/response/get
 67 2 8 12 7
sendSetRequest.js
in lib/request
 52 3 8 15 5
nodeTestReporter.js
in performance/reporters
 38 4 8 21 4
karmaBenchmarkCSVReporter.js
in performance/reporters
 38 3 8 21 4
CallResponse.js
in lib/response
 60 3 7 12 3
30 1 7 23 7
InvalidateResponse.js
in lib/response
 55 1 6 11 6
NullInPathError.js
in lib/errors
 15 1 6 40 6
18 2 6 33 4
gulp-perf.js
in build
 36 5 5 14 1
23 5 5 22 1
CSVFormatter.js
in performance/formatter
 32 2 5 16 3
node.js
in performance
 23 2 5 22 4
browser.js
in performance
 23 2 5 22 4
server.js
in root
 36 2 4 11 3
20 1 4 20 4
index.js
in performance/models/legacy
 34 4 4 12 1
flushGetRequest.js
in lib/request
 66 3 3 5 1
16 1 3 19 3
15 1 3 20 3
14 1 3 21 3
16 1 3 19 3
TimeoutScheduler.js
in lib/schedulers
 26 2 3 12 2
TriggerDataSource.js
in performance
 33 2 3 9 2
setGroupsIntoCache.js
in lib/response/set
 38 2 2 5 1
index.js
in lib
 16 2 2 13 1
hasOwn.js
in lib/support
 5 1 2 40 2
16 1 2 13 2
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...