File Complexity Overall
  • There are 27 files with units, with 4,093 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; 314 lines of code)
    • 6 slightly complex files (McCabe index sum 26-50; 2,058 lines of code)
    • 20 simple files (McCabe index sum 1-25; 1,721 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% | 7% | 50% | 42%
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
scala0% | 0% | 7% | 50% | 41%
ts0% | 0% | 0% | 0% | 100%
File Complexity per Logical Decomposition
primary
251+
126-250
51-125
26-50
1-25
facia-json0% | 0% | 37% | 21% | 40%
fapi-client0% | 0% | 0% | 60% | 39%
fapi-client-core0% | 0% | 0% | 0% | 100%
cdk0% | 0% | 0% | 0% | 100%
Most Complex Files (Top 27)

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
Config.scala
in facia-json/src/main/scala/com/gu/facia/client/models
314 7 54 17 18
ItemKicker.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
195 7 50 26 18
FAPI.scala
in fapi-client/src/main/scala/com/gu/facia/api
478 19 49 10 6
collection.scala
in fapi-client/src/main/scala/com/gu/facia/api/models
460 11 45 10 18
CustomSubnav.scala
in facia-json/src/main/scala/com/gu/facia/client/models
181 8 44 24 10
ContentApi.scala
in fapi-client/src/main/scala/com/gu/facia/api/contentapi
218 11 33 15 12
curatedcontent.scala
in fapi-client/src/main/scala/com/gu/facia/api/models
526 15 31 6 5
FaciaContentUtils.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
289 3 15 5 6
ResolvedMetaData.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
244 4 15 6 7
CardStyle.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
104 2 15 14 14
Response.scala
in fapi-client-core/src/main/scala/com/gu/facia/api
104 8 15 14 4
Backfill.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
90 2 13 14 8
collectionconfig.scala
in fapi-client/src/main/scala/com/gu/facia/api/models
179 6 13 7 7
front.scala
in fapi-client/src/main/scala/com/gu/facia/api/models
67 5 12 18 6
Collection.scala
in facia-json/src/main/scala/com/gu/facia/client/models
225 6 12 5 4
FaciaPressQueue.scala
in fapi-client/src/main/scala/com/gu/facia/api/models/faciapress
45 3 10 22 4
CustomSubnavService.scala
in fapi-client/src/main/scala/com/gu/facia/api
35 2 8 23 5
package.scala
in facia-json/src/main/scala/com/gu/facia/client/models
22 1 8 36 8
ContainerBrandingFinder.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
51 2 7 14 6
JodaFormat.scala
in facia-json/src/main/scala/com/gu/facia/client/json
31 2 7 23 6
ApiClient.scala
in facia-json/src/main/scala/com/gu/facia/client
56 3 5 9 3
IdsSearchQueries.scala
in fapi-client/src/main/scala/com/gu/facia/api/contentapi
27 1 4 15 4
ExternalLinks.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
37 2 4 11 2
ContentApiUtils.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
62 2 4 6 3
IntegerString.scala
in fapi-client/src/main/scala/com/gu/facia/api/utils
7 1 1 14 1
31 1 1 3 1
Environment.scala
in fapi-client-core/src/main/scala/com/gu/facia/client
15 1 1 7 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...