This class looks use really high number of components.

* Efferent coupling is 24, so this class uses 24 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks use really high number of components.

* Efferent coupling is 20, so this class uses 20 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.37 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 58, so this class uses 58 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 29)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.44 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 56, so this class uses 56 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (76, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=76)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 77)
* Component uses 76 operators

Maybe you should delegate some code to other objects.

This component contains in theory 0.64 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 308 logical lines of code
* Class has 311 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 78, so this class uses 78 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.37 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 44)
* Component uses 129 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 248 logical lines of code
* Class has 358 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 20, so this class uses 20 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.75 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.61 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.66 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.54 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.48 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=5)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.44 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.77 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.49 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.44 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 33, so this class uses 33 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 37)
* Component uses 129 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 13)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.03 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 213 logical lines of code
* Class has 439 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 24, so this class uses 24 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.6 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 46)
* Component uses 145 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.22 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 220 logical lines of code
* Class has 354 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.06 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 22, so this class uses 22 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 52)
* Component uses 135 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 13)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.23 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 230 logical lines of code
* Class has 351 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 22, so this class uses 22 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.49 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.64 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.55 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.54 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.46 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.47 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.37 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.72 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.64 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 23, so this class uses 23 different external components.

Maybe you should check why this class has lot of dependencies.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (34, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=38)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 97)
* Component uses 328 operators

Maybe you should delegate some code to other objects.

This component contains in theory 3.05 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 512 logical lines of code
* Class has 832 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 40, so this class uses 40 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.79 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 20, so this class uses 20 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.61 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.72 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 22, so this class uses 22 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.49 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.7 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 23, so this class uses 23 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.48 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.45 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 47)
* Component uses 145 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 254 logical lines of code
* Class has 343 lines of code

Maybe your class should not exceed 200 lines of logical code

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.62 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.78 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 20, so this class uses 20 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.5 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.54 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.46 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.83 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.71 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 23, so this class uses 23 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.81 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 204 logical lines of code
* Class has 365 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 14)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.72 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.53 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 81)
* Component uses 269 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 3.18 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 472 logical lines of code
* Class has 849 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 23, so this class uses 23 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.35 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.48 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.73 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.49 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.72 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.44 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 100)
* Component uses 165 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 72)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.32 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 243 logical lines of code
* Class has 350 lines of code

Maybe your class should not exceed 200 lines of logical code

This component contains in theory 0.53 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.39 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (13, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=9)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.94 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 211 logical lines of code
* Class has 409 lines of code

Maybe your class should not exceed 200 lines of logical code

This component contains in theory 0.68 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 214 logical lines of code
* Class has 363 lines of code

Maybe your class should not exceed 200 lines of logical code

This component contains in theory 0.49 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 15)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.73 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 61)
* Component uses 216 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.39 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 380 logical lines of code
* Class has 579 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 23, so this class uses 23 different external components.

Maybe you should check why this class has lot of dependencies.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (18, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=3)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 46)
* Component uses 150 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 15)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.77 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 233 logical lines of code
* Class has 405 lines of code

Maybe your class should not exceed 200 lines of logical code

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (35, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=18)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 39)
* Component uses 169 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.34 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 352 logical lines of code
* Class has 765 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 34, so this class uses 34 different external components.

Maybe you should check why this class has lot of dependencies.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks use really high number of components.

* Efferent coupling is 22, so this class uses 22 different external components.

Maybe you should check why this class has lot of dependencies.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (11, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=9)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.37 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 26, so this class uses 26 different external components.

Maybe you should check why this class has lot of dependencies.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.49 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.57 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 20, so this class uses 20 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.46 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (163, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=164)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 164)
* Component uses 163 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.6 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 659 logical lines of code
* Class has 768 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 146, so this class uses 146 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.43 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.61 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 36, so this class uses 36 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 38)
* Component uses 138 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 17)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.96 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 48)
* Component uses 172 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 19)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 1.55 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 254 logical lines of code
* Class has 452 lines of code

Maybe your class should not exceed 200 lines of logical code

This component contains in theory 0.53 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 24, so this class uses 24 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.43 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 33, so this class uses 33 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 22)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.5 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.63 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.83 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.96 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 230 logical lines of code
* Class has 346 lines of code

Maybe your class should not exceed 200 lines of logical code

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.77 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.52 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 28, so this class uses 28 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.35 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.59 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 130 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.12 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 273 logical lines of code
* Class has 322 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.44 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.6 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.51 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.52 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.44 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.42 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.91 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.39 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.59 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 131 operators

Maybe you should delegate some code to other objects.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 18)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.91 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 29)
* Component uses 102 operators

Maybe you should delegate some code to other objects.

This component contains in theory 0.71 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 230 logical lines of code
* Class has 391 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 56, so this class uses 56 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.63 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.8 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 32)
* Component uses 71 operators

Maybe you should delegate some code to other objects.

This component contains in theory 0.42 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 40)
* Component uses 110 operators

Maybe you should delegate some code to other objects.

This component contains in theory 0.81 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 233 logical lines of code
* Class has 421 lines of code

Maybe your class should not exceed 200 lines of logical code

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (11, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=6)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (19, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (16, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.35 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.52 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 30, so this class uses 30 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.45 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.45 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.88 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 223 logical lines of code
* Class has 348 lines of code

Maybe your class should not exceed 200 lines of logical code

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (78, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=79)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 79)
* Component uses 78 operators

Maybe you should delegate some code to other objects.

This component contains in theory 0.66 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 319 logical lines of code
* Class has 391 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 71, so this class uses 71 different external components.

Maybe you should check why this class has lot of dependencies.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=6)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.37 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.7 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.82 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.42 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 1.27 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=5)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.64 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.5 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=11)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.51 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.53 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.46 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.57 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 36)
* Component uses 150 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.32 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 350 logical lines of code
* Class has 548 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks use really high number of components.

* Efferent coupling is 25, so this class uses 25 different external components.

Maybe you should check why this class has lot of dependencies.

This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.

This component contains in theory 0.74 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.68 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.5 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.43 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks use really high number of components.

* Efferent coupling is 33, so this class uses 33 different external components.

Maybe you should check why this class has lot of dependencies.

This component contains in theory 0.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.135) than 2 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Statement (0.143)
* Wikibase\DataModel (0.19)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.122) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Statement (0.143)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.182) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\RestApi\Infrastructure\DataAccess (0.969)
* Wikibase\Lib\Store (0.25)
* Wikibase\Repo\RestApi\RouteHandlers (0.989)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.089) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Statement (0.143)
* Wikibase\Repo\RestApi\Domain\Services (0.301)
* Wikibase\Repo\RestApi\Domain\Model (0.135)

Packages should depend in the direction of stability.

This package is more stable (0.636) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\RestApi\Application\UseCases\PatchStatement (0.645)

Packages should depend in the direction of stability.

This package is more stable (0.412) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\RestApi\Application\UseCaseRequestValidation (0.437)

Packages should depend in the direction of stability.

This package is more stable (0.636) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\RestApi\Application\UseCases\PatchStatement (0.645)

Packages should depend in the direction of stability.

This package is more stable (0.437) than 49 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\RestApi\Application\UseCases\AddItemStatement (0.789)
* Wikibase\Repo\RestApi\Application\UseCases\AddPropertyStatement (0.789)
* Wikibase\Repo\RestApi\Application\UseCases\GetItem (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\GetSitelinks (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetSitelink (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemLabels (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemLabel (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemDescriptions (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemDescription (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemAliases (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemAliasesInLanguage (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemStatements (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\GetProperty (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyLabels (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyDescriptions (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyAliases (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyAliasesInLanguage (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyStatements (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemLabels (0.857)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemDescriptions (0.857)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemAliases (0.846)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveItemLabel (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveItemDescription (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveItemStatement (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\RemovePropertyLabel (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemovePropertyDescription (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemovePropertyStatement (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\ReplaceItemStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\ReplacePropertyStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\SetItemLabel (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\SetItemDescription (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyLabel (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyDescription (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\SetPropertyDescription (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\PatchProperty (0.826)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyLabels (0.862)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyDescriptions (0.862)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyAliases (0.846)
* Wikibase\Repo\RestApi\Application\UseCases\SetPropertyLabel (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\AddItemAliasesInLanguage (0.765)
* Wikibase\Repo\RestApi\Application\UseCases\AddPropertyAliasesInLanguage (0.765)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveSitelink (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\SetSitelink (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\PatchSitelinks (0.846)
* Wikibase\Repo\RestApi\Application\UseCases\CreateItem (0.714)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.367) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\RestApi\Application\Serialization (0.412)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.595) than 52 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\RestApi\Application\UseCases\GetItem (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\CreateItem (0.714)
* Wikibase\Repo\RestApi\Application\UseCases\GetSitelinks (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetSitelink (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemLabels (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemLabel (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemDescriptions (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemDescription (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemAliases (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemAliasesInLanguage (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\SetItemLabel (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\SetPropertyLabel (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\SetItemDescription (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\SetPropertyDescription (0.75)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemStatements (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\GetItemStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\AddItemStatement (0.789)
* Wikibase\Repo\RestApi\Application\UseCases\AddPropertyStatement (0.789)
* Wikibase\Repo\RestApi\Application\UseCases\ReplaceItemStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\ReplacePropertyStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveItemLabel (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemovePropertyLabel (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveItemDescription (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemovePropertyDescription (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveItemStatement (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\RemovePropertyStatement (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\PatchStatement (0.645)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyLabels (0.862)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyDescriptions (0.862)
* Wikibase\Repo\RestApi\Infrastructure\DataAccess (0.969)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemLabels (0.857)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemDescriptions (0.857)
* Wikibase\Repo\RestApi\Application\UseCases\PatchItemAliases (0.846)
* Wikibase\Repo\RestApi\Application\UseCases\PatchProperty (0.826)
* Wikibase\Repo\RestApi\Application\UseCases\PatchPropertyAliases (0.846)
* Wikibase\Repo\RestApi\Application\UseCases\PatchSitelinks (0.846)
* Wikibase\Repo\RestApi\Application\UseCases\GetProperty (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyStatement (0.636)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyStatements (0.667)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyLabel (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyLabels (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyDescription (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyDescriptions (0.6)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyAliasesInLanguage (0.692)
* Wikibase\Repo\RestApi\Application\UseCases\GetPropertyAliases (0.6)
* Wikibase\Repo\RestApi\Infrastructure (0.964)
* Wikibase\Repo\RestApi\Application\UseCases\AddItemAliasesInLanguage (0.765)
* Wikibase\Repo\RestApi\Application\UseCases\AddPropertyAliasesInLanguage (0.765)
* Wikibase\Repo\RestApi\Application\UseCases\RemoveSitelink (0.778)
* Wikibase\Repo\RestApi\Application\UseCases\SetSitelink (0.75)

Packages should depend in the direction of stability.

This package is more stable (0.507) than 6 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\Validators (0.532)
* Wikibase\Repo\ChangeOp\Deserialization (0.857)
* Wikibase\Repo\Merge (0.786)
* Wikibase\Repo\Merge\Validator (0.8)
* Wikibase\Lib\Normalization (0.778)
* Wikibase\Repo (0.704)

Packages should depend in the direction of stability.

This package is more stable (0.704) than 22 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Deserializers (0.786)
* Wikibase\Lib\Formatters (0.767)
* Wikibase\Repo\Content (0.784)
* Wikibase\Repo\Hooks (0.979)
* Wikibase\Repo\Store\Sql (0.866)
* Wikibase\Repo\ParserOutput (0.925)
* Wikibase\Repo\Api (0.957)
* Wikibase\Repo\Diff (0.86)
* Wikibase\Repo\LinkedData (0.86)
* Wikibase\Lib\Store\Sql (0.82)
* Wikibase\Repo\Interactors (0.848)
* Wikibase\Lib\Normalization (0.778)
* Wikibase\Repo\ChangeOp\Deserialization (0.857)
* Wikibase\Repo\Notifications (0.846)
* Wikibase\InternalSerialization (0.889)
* Wikibase\DataModel\Serializers (0.769)
* Wikibase\Lib\Store\Sql\Terms (0.884)
* Wikibase\Repo\Normalization (0.833)
* Wikibase\Lib\Modules (0.85)
* Wikibase\Repo\Hooks\Formatters (0.75)
* Wikibase\Repo\FederatedProperties (0.863)
* Wikibase\DataModel\Services\Statement\Filter (0.75)

Packages should depend in the direction of stability.

This package is more stable (0.368) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo (0.704)
* Wikibase\Lib\Store\Sql\Terms (0.884)
* Wikibase\Repo\Store\Sql\Terms (0.917)

Packages should depend in the direction of stability.

This package is more stable (0.667) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Lib\Formatters (0.767)

Packages should depend in the direction of stability.

This package is more stable (0.667) than 2 package(s) that it depends on.
The packages that are more stable are

* Wikibase\View (0.676)
* Wikibase\Lib\Formatters (0.767)

Packages should depend in the direction of stability.

This package is more stable (0.863) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\ParserOutput (0.925)
* Wikibase\Repo\Api (0.957)
* Wikibase\Repo\Specials (0.989)

Packages should depend in the direction of stability.

This package is more stable (0.638) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\Content (0.784)

Packages should depend in the direction of stability.

This package is more stable (0.577) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Services\Diff (0.654)
* Wikibase\Repo\Content (0.784)
* Wikibase\Repo (0.704)

Packages should depend in the direction of stability.

This package is more stable (0.784) than 2 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\Diff (0.86)
* Wikibase\Repo\Actions (0.946)

Packages should depend in the direction of stability.

This package is more stable (0.862) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\Store\Sql (0.866)

Packages should depend in the direction of stability.

This package is more stable (0.5) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\Content (0.784)

Packages should depend in the direction of stability.

This package is more stable (0.86) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\Api (0.957)

Packages should depend in the direction of stability.

This package is more stable (0.941) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo\Hooks (0.979)

Packages should depend in the direction of stability.

This package is more stable (0.532) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Repo (0.704)

Packages should depend in the direction of stability.

This package is more stable (0.676) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Lib\Formatters (0.767)
* Wikibase\Repo (0.704)
* Wikibase\DataModel\Services (0.8)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.164) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataAccess (0.495)
* Wikibase\Lib\Store (0.25)
* Wikibase\Lib\TermFallbackCache (0.529)

Packages should depend in the direction of stability.

This package is more stable (0.25) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataAccess (0.495)
* Wikibase\Lib\TermFallbackCache (0.529)
* Wikibase\Lib\Store\Sql\Terms (0.884)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.098) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataAccess (0.495)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.143) than 2 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel (0.19)
* Wikibase\DataModel\Exception (0.5)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.19) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Internal (0.333)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.033) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Statement (0.143)
* Wikibase\DataModel (0.19)
* Wikibase\DataModel\Term (0.056)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.1) than 2 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel (0.19)
* Wikibase\DataModel\Internal (0.333)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.432) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Services\Diff (0.654)

Packages should depend in the direction of stability.

This package is more stable (0.889) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\InternalSerialization\Deserializers (0.931)

Packages should depend in the direction of stability.

This package is more stable (0.654) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Services\Diff\Internal (0.857)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.143) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Statement (0.143)

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.

Packages should depend in the direction of stability.

This package is more stable (0.105) than 2 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Services\Entity (0.158)
* Wikibase\DataModel\Statement (0.143)

Packages should depend in the direction of stability.

This package is more stable (0.56) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Client (0.703)

Packages should depend in the direction of stability.

This package is more stable (0.703) than 10 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Lib\Formatters (0.767)
* Wikibase\Client\Hooks (0.968)
* Wikibase\DataModel\Deserializers (0.786)
* Wikibase\DataModel\Serializers (0.769)
* Wikibase\Lib\Store\Sql (0.82)
* Wikibase\Client\DataAccess\ParserFunctions (0.926)
* Wikibase\Client\DataAccess (0.811)
* Wikibase\Client\Changes (0.941)
* Wikibase\Client\RecentChanges (0.828)
* Wikibase\Lib\Store\Sql\Terms (0.884)

Packages should depend in the direction of stability.

This package is more stable (0.44) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Client\ParserOutput (0.65)
* Wikibase\Lib\Formatters (0.767)
* Wikibase\Client\Store (0.56)

Packages should depend in the direction of stability.

This package is more stable (0.811) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Lib\Formatters\Reference (0.875)

Packages should depend in the direction of stability.

This package is more stable (0.941) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Client\Hooks (0.968)

Packages should depend in the direction of stability.

This package is more stable (0.65) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikibase\Client\Hooks (0.968)

Packages should depend in the direction of stability.

This package is more stable (0.495) than 3 package(s) that it depends on.
The packages that are more stable are

* Wikibase\DataModel\Deserializers (0.786)
* Wikibase\Lib\Store\Sql (0.82)
* Wikibase\InternalSerialization (0.889)