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=10)
* 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.38 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 94 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.

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.

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=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.

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 (12, 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=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 (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.

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=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.

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=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.

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=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.

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=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.

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=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.

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=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.

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=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.

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

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

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=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.

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=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.

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=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.

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=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.

This component contains in theory 0.69 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 0 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
* 0 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=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 14)

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

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
* 0 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 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.

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=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.

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=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 (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 (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.

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=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.

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.

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=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.

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=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 (13, 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.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 3 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 (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.

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=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=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 (11, 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.

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=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.

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=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=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 (9, 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 class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 55)
* Component uses 174 operators

Maybe you should delegate some code to other objects.

This component contains in theory 2.1 bugs.

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

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 354 logical lines of code
* Class has 513 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 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
* 8 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
* 34 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 0.69 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 18 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 118 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.42 bugs.

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

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 260 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.51 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 10 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
* 8 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
* 12 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 55)
* Component uses 150 operators

Maybe you should delegate some code to other objects.

This component contains in theory 1.47 bugs.

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

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 306 logical lines of code
* Class has 467 lines of code

Maybe your class should not exceed 200 lines of logical code

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
* 20 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 51)
* Component uses 107 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 1.52 bugs.

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

Maybe you should check your unit tests for this class.

This class looks really long.

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

Maybe your class should not exceed 200 lines of logical code

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
* 38 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.55 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 6 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 (16, 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 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
* 28 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 13)

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

This component contains in theory 1.02 bugs.

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

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 202 logical lines of code
* Class has 286 lines of code

Maybe your class should not exceed 200 lines of logical code

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
* 32 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
* 6 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 13)

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

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
* 22 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This component contains in theory 1.17 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 0 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 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.129) than 1 package(s) that it depends on.
The packages that are more stable are

* App\Http\Requests (0.211)

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

* App\Models\Contracts (0.167)

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

* App\Exceptions (0.692)

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

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

* App\Console\Commands\Etl (0.845)

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

* App\Console\Commands\Etl (0.845)

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

* App\Http\Requests (0.211)
* App\Util\Requests (0.129)

Packages should depend in the direction of stability.

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

* App\Queries\Orders (0.75)
* App\Queries\AccountNotes (0.75)
* App\Queries\Permissions (0.667)
* App\Queries\AccountEvents (0.75)
* App\Queries\Subscriptions (0.75)
* App\Queries\Roles (0.75)
* App\Util\Storage (0.667)
* App\Queries\Addresses (0.75)
* App\Queries\Locations (0.5)
* App\Queries\Partners (0.833)
* App\Queries\OrderProducts (0.75)
* App\Policies (0.941)
* App\Queries\PaymentMethods (0.75)

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

This package is instable and abstract.