This class looks really complex.

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

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
* 1 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.45 bugs.

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

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
* 1 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
* 1 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 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.43 bugs.

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

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

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

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

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
* 1 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.74 bugs.

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

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
* 1 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 24)

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

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 7 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
* 2 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 80)
* Component uses 151 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 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
* 2 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 218 logical lines of code
* Class has 510 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.65 bugs.

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

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 1 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
* 9 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
* 0 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
* 0 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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.

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

Maybe you should check your unit tests for this class.

This class looks really long.

* Class has 261 logical lines of code
* Class has 326 lines of code

Maybe your class should not exceed 200 lines of logical code

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

Maybe you should check your unit tests for this class.

This component contains in theory 1.09 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 242 logical lines of code
* Class has 378 lines of code

Maybe your class should not exceed 200 lines of logical code

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
* 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 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
* 0 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 326 lines of code

Maybe your class should not exceed 200 lines of logical code

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
* 0 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
* 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 (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 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
* 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 depend in the direction of stability.

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

* FastForward\DevTools\Changelog\Manager (0.615)
* FastForward\DevTools\Changelog\Checker (0.714)
* FastForward\DevTools\License (0.625)

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

* FastForward\DevTools\Composer\Command (0.8)

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

* FastForward\DevTools\Console\Output (0.375)

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.