PhpMetrics report

Created at 2026-06-18 13:45:42 , with PHPMetrics v2.9.0 (Jean-François Lépine).

Violations

655

Information

106

Warnings

274

Errors

275

Criticals

Class Violations

Class	Violations
yoummday\api\core\config\Config Blob / God object error 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=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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 50) * Component uses 84 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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.	Blob / God object Too complex class code Too complex method code Probably bugged
yoummday\api\core\repository\Repository Probably bugged warning 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.	Probably bugged
yoummday\api\helper\BankingHelper Probably bugged warning 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.	Probably bugged
yoummday\api\helper\FeeHelper Blob / God object error 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=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.	Blob / God object
yoummday\api\helper\XmlHelper Probably bugged warning 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.	Probably bugged
yoummday\api\provider\ExternalHubspotDataProvider Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\provider\TimeslotProvider Probably bugged warning 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.	Probably bugged
yoummday\api\provider\PreferenceProvider Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\file\xlsx\XLSXInvoice Probably bugged warning 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.	Probably bugged
yoummday\api\file\pdf\YoummdayPDF Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class.	Probably bugged
yoummday\api\type\Image Probably bugged warning 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.	Probably bugged
yoummday\api\type\File Too complex method code error 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.	Too complex method code
yoummday\api\type\keycloak\KeycloakUser Too complex method code error 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.	Too complex method code
yoummday\api\type\AuthToken Probably bugged warning 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.	Probably bugged
yoummday\api\db\MigrationHelper Blob / God object error 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 107) * Component uses 341 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 2.56 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. Too long information This class looks really long. * Class has 488 logical lines of code * Class has 693 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\controller\Onboard Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 372) * Component uses 946 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 107) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 9.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. Too long information This class looks really long. * Class has 1188 logical lines of code * Class has 1546 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\controller\Money Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 51) * Component uses 143 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\controller\Manage Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 1604) * Component uses 4300 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 199) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 57.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. Too long information This class looks really long. * Class has 5646 logical lines of code * Class has 8422 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information This class looks use really high number of components. * Efferent coupling is 76, so this class uses 76 different external components. Maybe you should check why this class has lot of dependencies.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\controller\Common Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 542) * Component uses 1372 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 70) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 14.24 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. Too long information This class looks really long. * Class has 1867 logical lines of code * Class has 2798 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information This class looks use really high number of components. * Efferent coupling is 43, so this class uses 43 different external components. Maybe you should check why this class has lot of dependencies.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\controller\App Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 75) * Component uses 265 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 2.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. Too long information This class looks really long. * Class has 361 logical lines of code * Class has 594 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\controller\Provider Blob / God object error 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=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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 844) * Component uses 2363 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 167) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 26.31 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. Too long information This class looks really long. * Class has 2547 logical lines of code * Class has 3966 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information This class looks use really high number of components. * Efferent coupling is 55, so this class uses 55 different external components. Maybe you should check why this class has lot of dependencies.	Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\controller\Calendar Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\controller\Webhook Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 236) * Component uses 683 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 35) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 7.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. Too long information This class looks really long. * Class has 789 logical lines of code * Class has 1089 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\controller\Files Too complex method code error 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. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class.	Too complex method code Probably bugged
yoummday\api\controller\Client Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 278) * Component uses 791 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 35) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 8.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. Too long information This class looks really long. * Class has 1064 logical lines of code * Class has 1478 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\controller\DataProcessor Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\controller\Cron Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 930) * Component uses 2953 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 83) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 38.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. Too long information This class looks really long. * Class has 3727 logical lines of code * Class has 4248 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information This class looks use really high number of components. * Efferent coupling is 38, so this class uses 38 different external components. Maybe you should check why this class has lot of dependencies.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\controller\Test Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 90) * Component uses 268 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 26) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 2.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. Too long information This class looks really long. * Class has 354 logical lines of code * Class has 515 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\controller\Custreport Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 1387) * Component uses 4764 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 102) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 63.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. Too long information This class looks really long. * Class has 5054 logical lines of code * Class has 5957 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information This class looks use really high number of components. * Efferent coupling is 32, so this class uses 32 different external components. Maybe you should check why this class has lot of dependencies.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\controller\Report Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\controller\Main Blob / God object error 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=14) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 394) * Component uses 1269 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 40) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 12.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. Too long information This class looks really long. * Class has 2038 logical lines of code * Class has 2521 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information This class looks use really high number of components. * Efferent coupling is 218, so this class uses 218 different external components. Maybe you should check why this class has lot of dependencies.	Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\controller\Admin Blob / God object error 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=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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 157) * Component uses 520 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 6.16 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. Too long information This class looks really long. * Class has 737 logical lines of code * Class has 1376 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\controller\External Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 65) * Component uses 176 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 248 logical lines of code * Class has 432 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\controller\Tel Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 236) * Component uses 714 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 55) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 7.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. Too long information This class looks really long. * Class has 875 logical lines of code * Class has 1271 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\LegacyRequestRunner Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 64) * Component uses 168 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 49) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.24 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\object\Timeslot Blob / God object error 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=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. Probably bugged warning 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.	Blob / God object Probably bugged
yoummday\api\modules\Telephony\Inbound\Infrastructure\DB\DBServiceInboundTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 58) * Component uses 194 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 37) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 252 logical lines of code * Class has 284 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Inbound\Service\InboundCallRoutingService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 273) * Component uses 721 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 73) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 6.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. Too long information This class looks really long. * Class has 912 logical lines of code * Class has 1128 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\modules\Telephony\Inbound\Model\InboundCall Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Telephony\Inbound\Model\FreeswitchRouting Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 52) * Component uses 137 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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. Too long information This class looks really long. * Class has 234 logical lines of code * Class has 358 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Inbound\Controller\ManageInboundQueueSoundController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 54) * Component uses 138 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 35) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.29 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. Too long information This class looks really long. * Class has 208 logical lines of code * Class has 247 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Inbound\Controller\TelInboundLifecycleController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 68) * Component uses 212 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 33) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class. Too long information This class looks really long. * Class has 240 logical lines of code * Class has 249 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Inbound\Controller\ManageInboundController Too complex method code error 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.	Too complex method code
yoummday\api\modules\Telephony\Inbound\Controller\ProviderInboundController Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Telephony\Inbound\Controller\TelInboundVoicefileController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 53) * Component uses 161 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 52) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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.	Too complex class code Too complex method code Probably bugged
yoummday\api\modules\Telephony\Shared\Infrastructure\DB\DBServiceSharedTelephonyTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 113) * Component uses 427 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 4.25 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. Too long information This class looks really long. * Class has 590 logical lines of code * Class has 692 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Shared\Service\TelephonyAgentNotificationService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 62) * Component uses 138 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 54) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\modules\Telephony\Shared\Service\TelephonyAgentLifecycleService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Telephony\Shared\Service\CallWorkMinuteService Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 30) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Telephony\Shared\Service\TelSoundService Blob / God object error 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=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.	Blob / God object
yoummday\api\modules\Telephony\Shared\Service\FreeswitchService Blob / God object error 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 49) * Component uses 267 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 2.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. Too long information This class looks really long. * Class has 339 logical lines of code * Class has 459 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Shared\Service\TelService Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Telephony\Shared\Model\Incident Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Telephony\Shared\Model\Voicefile Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 46) * Component uses 140 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 1.26 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. Too long information This class looks really long. * Class has 248 logical lines of code * Class has 274 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Shared\Controller\ManageTelephonyVoicefileController Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 37) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 0.92 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.	Too complex method code Probably bugged
yoummday\api\modules\Telephony\Outbound\Infrastructure\DB\DBServiceOutboundTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 306) * Component uses 1236 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 28) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 13.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. Too long information This class looks really long. * Class has 1759 logical lines of code * Class has 2079 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Outbound\Service\OutboundJobFileService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 96) * Component uses 293 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 38) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 2.29 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. Too long information This class looks really long. * Class has 378 logical lines of code * Class has 439 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Outbound\Service\OutboundCallDataService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Telephony\Outbound\Service\OutboundCallStartService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Telephony\Outbound\Model\OutboundCallHistory Too complex method code error 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.	Too complex method code
yoummday\api\modules\Telephony\Outbound\Model\OutboundJob Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Telephony\Outbound\Model\OutboundCall Blob / God object error 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=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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 89) * Component uses 198 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 46) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 378 logical lines of code * Class has 435 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Outbound\Archive\OutboundCallArchive Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Telephony\Outbound\Controller\ProviderOutboundController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 164) * Component uses 442 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 35) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 3.76 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. Too long information This class looks really long. * Class has 539 logical lines of code * Class has 602 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Outbound\Controller\TelOutboundController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 58) * Component uses 182 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 30) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 265 logical lines of code * Class has 300 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Telephony\Outbound\Controller\ManageOutboundController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 189) * Component uses 474 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 101) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 4.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. Too long information This class looks really long. * Class has 598 logical lines of code * Class has 707 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information This class looks use really high number of components. * Efferent coupling is 31, so this class uses 31 different external components. Maybe you should check why this class has lot of dependencies.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\modules\Telephony\Outbound\Controller\CronOutboundController Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\ProjectManagement\Infrastructure\DB\DBServiceProjectManagementContractsTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 57) * Component uses 189 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 32) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 269 logical lines of code * Class has 278 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\ProjectManagement\Infrastructure\DB\DBServiceProjectManagementModulePreferencesTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 80) * Component uses 325 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 3.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. Too long information This class looks really long. * Class has 476 logical lines of code * Class has 536 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\ProjectManagement\Controller\ProviderJobsController Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 27) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class.	Too complex method code Probably bugged
yoummday\api\modules\ProjectManagement\Controller\ManageProjectsController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 74) * Component uses 148 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 37) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.3 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. Too long information This class looks really long. * Class has 230 logical lines of code * Class has 258 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\ProjectManagement\Controller\ManageModulePreferencesController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 149) * Component uses 471 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 74) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 3.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. Too long information This class looks really long. * Class has 524 logical lines of code * Class has 549 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\ProjectManagement\Controller\ManageContractsController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 114) * Component uses 243 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 67) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.85 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. Too long information This class looks really long. * Class has 301 logical lines of code * Class has 317 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\ProjectManagement\Controller\ProviderContractsController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 114) * Component uses 250 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 92) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.95 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. Too long information This class looks really long. * Class has 297 logical lines of code * Class has 310 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\WorkforceOrganization\Infrastructure\DB\DBServiceWorkforceOrganizationTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 48) * Component uses 181 operators Maybe you should delegate some code to other objects. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 253 logical lines of code * Class has 283 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Probably bugged Too long
yoummday\api\modules\WorkforceOrganization\Controller\ManageWorkforceOrganizationController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 84) * Component uses 198 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 66) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 284 logical lines of code * Class has 311 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Invoice\Infrastructure\DB\DBServiceInvoiceTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 73) * Component uses 226 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 2.04 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. Too long information This class looks really long. * Class has 407 logical lines of code * Class has 468 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Invoice\Service\InvoiceService Too complex method code error 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.	Too complex method code
yoummday\api\modules\Finance\Invoice\Service\InvoiceDataService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 147) * Component uses 418 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 130) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 4.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. Too long information This class looks really long. * Class has 432 logical lines of code * Class has 502 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Invoice\Service\XMLInvoiceService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 86) * Component uses 312 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 48) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 3.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. Too long information This class looks really long. * Class has 497 logical lines of code * Class has 523 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Invoice\Service\PDFInvoiceService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 141) * Component uses 423 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 114) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 6.02 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. Too long information This class looks really long. * Class has 589 logical lines of code * Class has 635 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Invoice\Controller\InvoiceCronController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 90) * Component uses 229 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 33) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 2.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. Too long information This class looks really long. * Class has 327 logical lines of code * Class has 343 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Invoice\Controller\InvoiceController Too complex method code error 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. Probably bugged warning This component contains in theory 1.04 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.	Too complex method code Probably bugged
yoummday\api\modules\Finance\Shared\Infrastructure\DB\DBServiceFinanceSharedTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 123) * Component uses 479 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 27) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 4.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. Too long information This class looks really long. * Class has 641 logical lines of code * Class has 782 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Shared\Service\ExchangeService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Finance\Shared\Service\PaymentProvisionService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 47) * Component uses 266 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 2.14 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. Too long information This class looks really long. * Class has 322 logical lines of code * Class has 399 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Shared\Service\VatService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Finance\Shared\Service\VatIdCheckService Too complex method code error 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. Probably bugged warning This component contains in theory 0.56 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.	Too complex method code Probably bugged
yoummday\api\modules\Finance\Shared\Model\ExtraFee Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\modules\Finance\Shared\Controller\AbstractFinanceController Too complex method code error 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.	Too complex method code
yoummday\api\modules\Finance\Payments\Infrastructure\DB\DBServicePaymentsTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 202) * Component uses 783 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 23) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 8.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. Too long information This class looks really long. * Class has 1027 logical lines of code * Class has 1281 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Payments\Service\BalanceViewService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 64) * Component uses 144 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 64) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.31 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\modules\Finance\Payments\Service\PaymentImportService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 112) * Component uses 360 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 77) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 3.24 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. Too long information This class looks really long. * Class has 401 logical lines of code * Class has 471 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Payments\Service\PaymentService Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (14, 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 107) * Component uses 313 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 3.29 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. Too long information This class looks really long. * Class has 398 logical lines of code * Class has 552 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Payments\Service\ExternalPaymentsWorker Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 77) * Component uses 243 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 50) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 251 logical lines of code * Class has 292 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Payments\Service\PaypalService Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Finance\Payments\Model\Payment Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 66) * Component uses 174 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 30) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.19 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. Too long information This class looks really long. * Class has 236 logical lines of code * Class has 251 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Payments\Object\PaymentPair Blob / God object error 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=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.	Blob / God object
yoummday\api\modules\Finance\Payments\Controller\BalanceController Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Finance\Payments\Controller\PayoutController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 47) * Component uses 129 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\modules\Finance\Payments\Controller\PaymentIngressController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 70) * Component uses 167 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 44) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.3 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. Too long information This class looks really long. * Class has 204 logical lines of code * Class has 216 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\modules\Finance\Payments\Controller\PaymentController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 48) * Component uses 100 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 32) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\modules\Finance\BonusUpload\Infrastructure\DB\DBServiceBonusUploadTrait Probably bugged warning This component contains in theory 0.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. Too long information This class looks really long. * Class has 204 logical lines of code * Class has 252 lines of code Maybe your class should not exceed 200 lines of logical code	Probably bugged Too long
yoummday\api\modules\Finance\BonusUpload\Service\BonusPaymentImportService Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Finance\BonusUpload\Model\BonusList Blob / God object error 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.	Blob / God object
yoummday\api\modules\Finance\BonusUpload\Repository\BonusListRepository Probably bugged warning 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.	Probably bugged
yoummday\api\modules\Finance\BonusUpload\Controller\BonusController Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 86) * Component uses 220 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 47) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.99 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. Too long information This class looks really long. * Class has 288 logical lines of code * Class has 314 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\model\Onboarding Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 46) * Component uses 131 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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. Too long information This class looks really long. * Class has 289 logical lines of code * Class has 329 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\model\Recruitment Too complex method code error 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.	Too complex method code
yoummday\api\model\Model Probably bugged warning This component contains in theory 1.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.	Probably bugged
yoummday\api\model\collection\CompanyRoleCollection Blob / God object error 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.	Blob / God object
yoummday\api\model\collection\KeycloakGroupCollection Blob / God object error 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=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.	Blob / God object
yoummday\api\model\Quest Too complex method code error 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. Probably bugged warning This component contains in theory 0.56 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.	Too complex method code Probably bugged
yoummday\api\model\Contract Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (14, 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. Too complex method code error 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. Probably bugged warning This component contains in theory 0.92 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.	Blob / God object Too complex method code Probably bugged
yoummday\api\model\UserOnlinePresence Probably bugged warning 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.	Probably bugged
yoummday\api\model\UserSp Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (33, 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 186) * Component uses 642 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 36) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 6.24 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. Too long information This class looks really long. * Class has 1107 logical lines of code * Class has 1234 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\model\OnboardMeeting Too complex method code error 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. Probably bugged warning This component contains in theory 0.67 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.	Too complex method code Probably bugged
yoummday\api\model\Document Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\model\UserCu Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 57) * Component uses 191 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 30) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class. Too long information This class looks really long. * Class has 394 logical lines of code * Class has 425 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\model\User Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (98, excluding getters and setters) * object has a high Lack of cohesion of methods (LCOM=23) * object knows everything (and use lot of external classes) Maybe you should reducing the number of methods splitting this object in many sub objects. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 192) * Component uses 809 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 23) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 7.25 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. Too long information This class looks really long. * Class has 1330 logical lines of code * Class has 1642 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\model\Training Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 48) * Component uses 108 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\model\Address Too complex method code error 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. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class.	Too complex method code Probably bugged
yoummday\api\model\WebCallbackDataDto Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\model\Message Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 66) * Component uses 158 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 35) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.2 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. Too long information This class looks really long. * Class has 261 logical lines of code * Class has 289 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\model\QualityCheck Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 82) * Component uses 173 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 33) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.28 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. Too long information This class looks really long. * Class has 272 logical lines of code * Class has 299 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\model\Module Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (29, 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 186) * Component uses 444 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 3.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. Too long information This class looks really long. * Class has 659 logical lines of code * Class has 790 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\model\CronJob Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 53) * Component uses 194 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 32) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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.	Too complex class code Too complex method code Probably bugged
yoummday\api\service\MSGraphAPI Probably bugged warning 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.	Probably bugged
yoummday\api\service\DBServiceUserTrait Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (154, 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 531) * Component uses 2007 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 83) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 26.08 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. Too long information This class looks really long. * Class has 3112 logical lines of code * Class has 3942 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\service\Mp3WaveformService Too complex method code error 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. Probably bugged warning This component contains in theory 0.92 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.	Too complex method code Probably bugged
yoummday\api\service\FileService Probably bugged warning 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.	Probably bugged
yoummday\api\service\QualityCheckExportService Blob / God object error 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=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. Probably bugged warning 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.	Blob / God object Probably bugged
yoummday\api\service\Telefonica\BillingService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 83) * Component uses 228 operators Maybe you should delegate some code to other objects. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 370 logical lines of code * Class has 465 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Probably bugged Too long
yoummday\api\service\Telefonica\PartsProcessor Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 498) * Component uses 1699 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 121) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 18.01 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. Too long information This class looks really long. * Class has 1337 logical lines of code * Class has 1570 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\CalendarService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\ProjectService Probably bugged warning 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.	Probably bugged
yoummday\api\service\DBServiceReportTrait Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (84, 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 619) * Component uses 2455 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 62) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 28.13 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. Too long information This class looks really long. * Class has 2804 logical lines of code * Class has 3331 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\QualityCheckDetailService Probably bugged warning 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.	Probably bugged
yoummday\api\service\CsvParser\CsvParser Too complex method code error 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.	Too complex method code
yoummday\api\service\TasagService Probably bugged warning 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.	Probably bugged
yoummday\api\service\AppService Probably bugged warning 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.	Probably bugged
yoummday\api\service\DBService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 51) * Component uses 135 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 1.1 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. Too long information This class looks really long. * Class has 250 logical lines of code * Class has 290 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\DBServicePlanningTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 125) * Component uses 475 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 4.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. Too long information This class looks really long. * Class has 634 logical lines of code * Class has 785 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\StatisticService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 97) * Component uses 240 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 44) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 2.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. Too long information This class looks really long. * Class has 295 logical lines of code * Class has 421 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\VodafoneSyncService Blob / God object error 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=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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 83) * Component uses 223 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 26) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 330 logical lines of code * Class has 456 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\DBServiceRecruitmentTrait Probably bugged warning This component contains in theory 0.95 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. Too long information This class looks really long. * Class has 246 logical lines of code * Class has 368 lines of code Maybe your class should not exceed 200 lines of logical code	Probably bugged Too long
yoummday\api\service\DBServiceAiTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 37) * Component uses 201 operators Maybe you should delegate some code to other objects. Probably bugged warning This component contains in theory 2 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. Too long information This class looks really long. * Class has 378 logical lines of code * Class has 478 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Probably bugged Too long
yoummday\api\service\GeocodeService Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 26) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\DBServiceWebCallbackTokenTrait Probably bugged warning 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.	Probably bugged
yoummday\api\service\ICalendarService Too complex method code error 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. Probably bugged warning This component contains in theory 1.04 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.	Too complex method code Probably bugged
yoummday\api\service\ExternalPortalUrlConstructionService Probably bugged warning 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.	Probably bugged
yoummday\api\service\CalendarOptionsService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\UserRoamingCheckService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\Mp3CutterService Probably bugged warning This component contains in theory 1.08 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.	Probably bugged
yoummday\api\service\DBServiceWebCallbackTrait Probably bugged warning 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.	Probably bugged
yoummday\api\service\SFTPService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 45) * Component uses 160 operators Maybe you should delegate some code to other objects. Probably bugged warning This component contains in theory 1.07 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. Too long information This class looks really long. * Class has 260 logical lines of code * Class has 343 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Probably bugged Too long
yoummday\api\service\HubspotService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 84) * Component uses 201 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 39) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 3.09 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. Too long information This class looks really long. * Class has 333 logical lines of code * Class has 398 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\TimezoneService Probably bugged warning This component contains in theory 1.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.	Probably bugged
yoummday\api\service\GeoIPService Too complex method code error 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.	Too complex method code
yoummday\api\service\LegacyUserProvisioningService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 55) * Component uses 123 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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.	Too complex class code Too complex method code Probably bugged
yoummday\api\service\OnboardingService Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\HelperService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 58) * Component uses 183 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class. Too long information This class looks really long. * Class has 219 logical lines of code * Class has 317 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\DBServiceTalentDashboardStatsTrait Too complex method code error 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. Probably bugged warning This component contains in theory 1.3 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. Too long information This class looks really long. * Class has 405 logical lines of code * Class has 456 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex method code Probably bugged Too long
yoummday\api\service\QualityCheckCreateService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\DocumentService Too complex method code error 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.	Too complex method code
yoummday\api\service\DBServiceOthersTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 353) * Component uses 1443 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 17.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. Too long information This class looks really long. * Class has 2119 logical lines of code * Class has 2623 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\WebsocketNotifyService Probably bugged warning 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.	Probably bugged
yoummday\api\service\ChatCharlieMigrationService Too complex method code error 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.	Too complex method code
yoummday\api\service\smsService\MessageBirdService Probably bugged warning 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.	Probably bugged
yoummday\api\service\HubspotSyncService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 110) * Component uses 252 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 2.2 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. Too long information This class looks really long. * Class has 437 logical lines of code * Class has 627 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\service\ShiftOverviewService Probably bugged warning 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.	Probably bugged
yoummday\api\service\AdminService Blob / God object error 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=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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 154) * Component uses 390 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 28) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 3.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. Too long information This class looks really long. * Class has 527 logical lines of code * Class has 710 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\Dtag\BillingService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 54) * Component uses 171 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class. Too long information This class looks really long. * Class has 237 logical lines of code * Class has 300 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\PDFDocumentService Too complex method code error 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. Probably bugged warning This component contains in theory 2.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. Too long information This class looks really long. * Class has 255 logical lines of code * Class has 314 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex method code Probably bugged Too long
yoummday\api\service\ZendeskService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\keycloak\KeycloakApiService Probably bugged warning 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.	Probably bugged
yoummday\api\service\keycloak\KeycloakApiServiceStub Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 146) * Component uses 307 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 106) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 2.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. Too long information This class looks really long. * Class has 314 logical lines of code * Class has 379 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\keycloak\KeycloakGroupService Blob / God object error 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=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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 55) * Component uses 134 operators Maybe you should delegate some code to other objects. Probably bugged warning This component contains in theory 0.99 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. Too long information This class looks really long. * Class has 216 logical lines of code * Class has 340 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Probably bugged Too long
yoummday\api\service\keycloak\KeycloakUserService Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (28, 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 77) * Component uses 246 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 2.07 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. Too long information This class looks really long. * Class has 408 logical lines of code * Class has 682 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\DBServiceTelephonyTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 315) * Component uses 1392 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 15.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. Too long information This class looks really long. * Class has 1822 logical lines of code * Class has 2246 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\DBServiceHubspotSyncTrait Probably bugged warning 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.	Probably bugged
yoummday\api\service\OutputFileFormattingService Probably bugged warning 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.	Probably bugged
yoummday\api\service\MailerService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 46) * Component uses 233 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 28) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 231 logical lines of code * Class has 292 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\LogService Too complex method code error 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. Probably bugged warning This component contains in theory 0.76 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.	Too complex method code Probably bugged
yoummday\api\service\TalentDashboardStatsService Too complex method code error 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. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class.	Too complex method code Probably bugged
yoummday\api\service\AroundhomeService Too complex method code error 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. Probably bugged warning This component contains in theory 1.04 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.	Too complex method code Probably bugged
yoummday\api\service\DBServiceModuleContractTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 310) * Component uses 1257 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 13.13 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. Too long information This class looks really long. * Class has 1728 logical lines of code * Class has 2107 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\EmlService Probably bugged warning 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.	Probably bugged
yoummday\api\service\AiQaService Blob / God object error A blob object (or "god class") does not follow the Single responsibility principle. * object has lot of public methods (15, 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 47) * Component uses 122 operators Maybe you should delegate some code to other objects. Probably bugged warning This component contains in theory 1.13 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. Too long information This class looks really long. * Class has 259 logical lines of code * Class has 409 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Probably bugged Too long
yoummday\api\service\MessageService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 42) * Component uses 127 operators Maybe you should delegate some code to other objects. Probably bugged warning 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 * testsuites has dependency to this class. Maybe you should check your unit tests for this class. Too long information This class looks really long. * Class has 251 logical lines of code * Class has 351 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Probably bugged Too long
yoummday\api\service\CompanyMemberService Probably bugged warning 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.	Probably bugged
yoummday\api\service\GPSService Too complex method code error 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.	Too complex method code
yoummday\api\service\UserService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 141) * Component uses 330 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 3.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. Too long information This class looks really long. * Class has 608 logical lines of code * Class has 743 lines of code Maybe your class should not exceed 200 lines of logical code Too dependent information 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.	Too complex class code Too complex method code Probably bugged Too long Too dependent
yoummday\api\service\DBServiceMessageTrait Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 121) * Component uses 474 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 28) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 4.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. Too long information This class looks really long. * Class has 771 logical lines of code * Class has 993 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\WebCallbackService Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\service\ModuleService Blob / God object error 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. Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 62) * Component uses 157 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 1.14 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. Too long information This class looks really long. * Class has 248 logical lines of code * Class has 341 lines of code Maybe your class should not exceed 200 lines of logical code	Blob / God object Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\QuestService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 81) * Component uses 183 operators Maybe you should delegate some code to other objects. Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 81) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 232 logical lines of code * Class has 290 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\service\CookieService Probably bugged warning 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.	Probably bugged
yoummday\api\service\ModulePreferencesService Probably bugged warning 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.	Probably bugged
yoummday\api\service\PermissionService Too complex class code error This class looks really complex. * Algorithms are complex (Total cyclomatic complexity of class is 80) * Component uses 190 operators Maybe you should delegate some code to other objects. Too complex method code error 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. Probably bugged warning This component contains in theory 1.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. Too long information This class looks really long. * Class has 369 logical lines of code * Class has 545 lines of code Maybe your class should not exceed 200 lines of logical code	Too complex class code Too complex method code Probably bugged Too long
yoummday\api\Customer\VodafoneZiggo\DataFitter\DataFitter Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\Action\VodafoneVoiceFileReportAction Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\Action\SyncTalentsToADAction Too complex method code error This class looks really complex. * Algorithms are complex (Max cyclomatic complexity of class methods is 31) Maybe you should delegate some code to other objects or split complex method. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\Action\MatchAzureAction Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\Action\JsmdVoiceFileReportAction Too complex method code error 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. Probably bugged warning 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.	Too complex method code Probably bugged
yoummday\api\Action\Report\UploadVerivoxVoiceTranscriptionReportAction Probably bugged warning 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.	Probably bugged
yoummday\api\repository\TalentRepository Probably bugged warning This component contains in theory 0.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.	Probably bugged
PlatformTaxTransparencyAct\Notify\Factory\MessageFactory Probably bugged warning 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.	Probably bugged
PlatformTaxTransparencyAct\Notify\Factory\XMLReportedSellerFactory Probably bugged warning This component contains in theory 0.97 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.	Probably bugged

Package Violations

Package	Violations
yoummday\api\core Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.047) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\core\exception (0.091)	Stable Dependencies Principle
yoummday\api\core\exception Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\core\exception\ExternalService Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\core\log Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\core\config Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.474) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\core\error\service Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\core\repository\QueryFactory Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\core\repository\attribute Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.333) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\helper Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning 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 * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\Interface Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\dispatcher Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\file\xlsx Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.6) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Dependencies Principle
yoummday\api\file\html Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\type Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning 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 * yoummday\api\helper (0.364) * yoummday\api (0.333) * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\type\keycloak Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.111) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\core\error\service (0.125)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\Exception Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\enum\trait Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\enum Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\Transformer\Request Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\DataTransferObject Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.182) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\model (0.24)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\DataTransferObject\Response Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.297) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\object (0.5)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\User\Infrastructure\Persistence Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\User\Application\Exception Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.6) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Dependencies Principle
yoummday\api\User\Domain\Service Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\User\Domain\Contract\Persistence Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.167) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\model (0.24)	Stable Dependencies Principle
yoummday\api\modules\Telephony\Inbound\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Telephony\Inbound\Service Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.897) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\modules\Telephony\Outbound\Controller (0.917)	Stable Dependencies Principle
yoummday\api\modules\Telephony\Inbound\Model Stable Dependencies Principle warning 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 * yoummday\api\service (0.648)	Stable Dependencies Principle
yoummday\api\modules\Telephony\Shared\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Telephony\Shared\Service Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.706) than 2 package(s) that it depends on. The packages that are more stable are * yoummday\api\Customer\DreiAt (0.75) * yoummday\api\modules\Telephony\Shared\Repository (0.833)	Stable Dependencies Principle
yoummday\api\modules\Telephony\Shared\Model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.189) than 2 package(s) that it depends on. The packages that are more stable are * yoummday\api\model (0.24) * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\modules\Telephony\Outbound\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Telephony\Outbound\Model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.304) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\modules\ProjectManagement\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\ProjectManagement\Service Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.556) than 2 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648) * yoummday\api\service\ShiftPlan (0.577)	Stable Dependencies Principle
yoummday\api\modules\WorkforceOrganization\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\Invoice\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\Invoice\Model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\Shared\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\Shared\Service Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.475) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\modules\Finance\Shared\Dto Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\Shared\Model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\Payments\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\Payments\Model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.179) than 3 package(s) that it depends on. The packages that are more stable are * yoummday\api\model (0.24) * yoummday\api\modules\Telephony\Shared\Model (0.189) * yoummday\api\modules\Finance\BonusUpload\Model (0.471)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\modules\Finance\Payments\Object Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.421) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\modules\Finance\BonusUpload\Model (0.471)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\modules\Finance\BonusUpload\Infrastructure\DB Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\modules\Finance\BonusUpload\Service\CsvParser Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.333) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service\CsvParser (0.333)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\modules\Finance\BonusUpload\Model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.471) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\modules\Finance\BonusUpload\Object Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.222) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\model (0.24)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.24) than 5 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648) * yoummday\api\helper (0.364) * yoummday\api (0.333) * yoummday\api\Interface (0.538) * yoummday\api\modules\Telephony\Outbound\Model (0.304)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\model\interface Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.056) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Dependencies Principle
yoummday\api\service Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.648) than 10 package(s) that it depends on. The packages that are more stable are * yoummday\api\Domain\Infrastructure\User\Persistence (0.778) * yoummday\api\Domain\Infrastructure\User\Persistence\UserSp (0.692) * yoummday\api\modules\Telephony\Outbound\Repository (0.917) * yoummday\api\modules\Telephony\Shared\Service (0.706) * yoummday\api\modules\Finance\Payments\Service (0.686) * yoummday\api\service\keycloak (0.806) * yoummday\api\provider (0.778) * yoummday\api\model\collection (0.7) * yoummday\api\User\Application\Service (0.895) * yoummday\api\Exception\User (0.667)	Stable Dependencies Principle
yoummday\api\service\CsvParser Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.333) than 2 package(s) that it depends on. The packages that are more stable are * yoummday\api\Exception (0.4) * yoummday\api\modules\Finance\BonusUpload\Service\CsvParser (0.333)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\service\ExternalIdMapping Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.333) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Abstractions Principle Stable Dependencies Principle
yoummday\api\service\ShiftPlan Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.577) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Dependencies Principle
yoummday\api\service\smsService Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.6) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\service (0.648)	Stable Dependencies Principle
yoummday\api\Customer\VodafoneZiggo\DataFitter Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\entity Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
yoummday\api\Domain\Infrastructure\User\Persistence Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.778) than 2 package(s) that it depends on. The packages that are more stable are * yoummday\api\Domain\Infrastructure\User\Persistence\UserCu (0.857) * yoummday\api\Domain\Infrastructure\User\Persistence\UserPm (0.857)	Stable Dependencies Principle
yoummday\api\Domain\Infrastructure\User\Persistence\UserSp Stable Dependencies Principle warning Packages should depend in the direction of stability. This package is more stable (0.692) than 1 package(s) that it depends on. The packages that are more stable are * yoummday\api\Domain\Infrastructure\User\Persistence (0.778)	Stable Dependencies Principle
PlatformTaxTransparencyAct\Notify\Model Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
PlatformTaxTransparencyAct\Generate\Console Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract.	Stable Abstractions Principle
PlatformTaxTransparencyAct\Generate\Entity Stable Abstractions Principle warning Packages should be either abstract and stable or concrete and instable. This package is instable and abstract. Stable Dependencies Principle warning 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 * PlatformTaxTransparencyAct\Generate\XML (0.667)	Stable Abstractions Principle Stable Dependencies Principle