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

* object has lot of public methods (48, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=48)
* 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 14)

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.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.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.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 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 12)

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 15)

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 15)

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

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* Component uses 141 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 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 class looks really long.

* Class has 264 logical lines of code
* Class has 328 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 12)

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

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 34)
* Component uses 118 operators

Maybe you should delegate some code to other objects.

This component contains in theory 0.98 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 239 logical lines of code
* Class has 320 lines of code

Maybe your class should not exceed 200 lines of logical code

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 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 class looks really complex.

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

Maybe you should delegate some code to other objects.

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 302 logical lines of code
* Class has 362 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 15)

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

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 59)
* Component uses 125 operators

Maybe you should delegate some code to other objects.

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 really long.

* Class has 240 logical lines of code
* Class has 419 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 33)
* Component uses 112 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.

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=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.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 class looks really long.

* Class has 238 logical lines of code
* Class has 352 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 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 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.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.9 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 (10, 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 36)
* Component uses 131 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.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 class looks really long.

* Class has 326 logical lines of code
* Class has 388 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 (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=8)
* 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.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.

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

* object has lot of public methods (80, 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 38)
* Component uses 195 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.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 class looks really long.

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

Maybe your class should not exceed 200 lines of logical code

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 17)
* Component uses 100 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 227 logical lines of code
* Class has 294 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks really complex.

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

Maybe you should delegate some code to other objects.

This component contains in theory 0.84 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 219 logical lines of code
* Class has 335 lines of code

Maybe your class should not exceed 200 lines of logical code

This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 62)
* Component uses 205 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.86 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 432 logical lines of code
* Class has 676 lines of code

Maybe your class should not exceed 200 lines of logical code

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.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 (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.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 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 (39, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=17)
* 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 22)
* Component uses 128 operators

Maybe you should delegate some code to other objects.

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 really long.

* Class has 304 logical lines of code
* Class has 443 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 (21, 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 component contains in theory 0.38 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.58 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 14)

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

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.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 (Max cyclomatic complexity of class methods is 12)

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 12)

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.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 61)
* Component uses 232 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.89 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 349 logical lines of code
* Class has 374 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 48, so this class uses 48 different external components.

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

Packages should depend in the direction of stability.

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

* Snicco\Component\Psr7ErrorHandler\Log (0.6)

Packages should depend in the direction of stability.

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

* Snicco\Component\Psr7ErrorHandler\Identifier (0.333)

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.368) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\Kernel\Exception (0.4)

Packages should depend in the direction of stability.

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

* Snicco\Component\EventDispatcher\ListenerFactory (0.667)
* Snicco\Component\EventDispatcher\Exception (0.556)

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.538) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\Templating\ViewFactory (0.769)

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.083) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\Templating\Exception (0.3)

Packages should depend in the direction of stability.

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

* Snicco\Component\BetterWPHooks (0.714)
* Snicco\Component\BetterWPHooks\EventFactory (0.75)

Packages should depend in the direction of stability.

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

* Snicco\Component\BetterWPCLI (0.704)

Packages should depend in the direction of stability.

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

* Snicco\Component\BetterWPCLI\CommandLoader (0.75)
* Snicco\Component\BetterWPCLI\Logger (0.75)
* Snicco\Component\BetterWPCLI\Style (0.889)

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.5) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\BetterWPCLI (0.704)

Packages should depend in the direction of stability.

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

* Snicco\Component\BetterWPCLI\Synopsis (0.5)
* Snicco\Component\BetterWPCLI (0.704)

Packages should depend in the direction of stability.

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

* Snicco\Component\Eloquent (0.895)

Packages should depend in the direction of stability.

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

* Snicco\Component\Eloquent\Illuminate (0.867)
* Snicco\Component\Eloquent (0.895)

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.5) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\Session (0.6)

Packages should depend in the direction of stability.

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

* Snicco\Component\Session (0.6)
* Snicco\Component\Session\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.286) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\Session (0.6)

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.429) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\HttpRouting\Routing\Condition (0.5)

Packages should depend in the direction of stability.

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

* Snicco\Component\HttpRouting\Routing\RouteLoader (0.833)
* Snicco\Component\HttpRouting\Routing\RoutingConfigurator (0.8)

Packages should depend in the direction of stability.

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

* Snicco\Component\HttpRouting\Routing (0.781)

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.364) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\Psr7ErrorHandler (0.52)

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.26) than 3 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\HttpRouting\Routing\UrlMatcher (0.75)
* Snicco\Component\HttpRouting\Http (0.632)
* Snicco\Component\HttpRouting\Http\Response (0.286)

Packages should depend in the direction of stability.

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

* Snicco\Component\HttpRouting\Controller (0.875)
* Snicco\Component\HttpRouting\Exception (0.667)
* Snicco\Component\HttpRouting (0.714)
* Snicco\Component\HttpRouting\Routing\UrlMatcher (0.75)
* Snicco\Component\HttpRouting\Routing\UrlGenerator (0.5)
* Snicco\Component\HttpRouting\Http (0.632)
* Snicco\Component\Psr7ErrorHandler (0.52)

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.385) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\SignedUrl (0.565)

Packages should depend in the direction of stability.

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

* Snicco\Component\BetterWPMail\Exception (0.5)

Packages should depend in the direction of stability.

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

* Snicco\Component\BetterWPMail (0.722)

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

* Snicco\Component\BetterWPMail (0.722)

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.429) than 1 package(s) that it depends on.
The packages that are more stable are

* Snicco\Component\BetterWPMail (0.722)

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

* Snicco\Component\Psr7ErrorHandler (0.52)

Packages should depend in the direction of stability.

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

* Snicco\Middleware\WPNonce (0.889)

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.