Violations
210
Information
30
Warnings
104
Errors
76
Criticals
0

Class Violations

Class Violations
App\Traits\GlobalMethods
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Traits\MissingCommissionsTrait
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.84 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 234 logical lines of code
* Class has 359 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
App\Traits\ExcelReport
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Traits\Stripe\StripeCustomer
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=10)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 47)
* Component uses 107 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 25)

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
* 0 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
App\Traits\Stripe\StripeSubscription
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (19, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 91)
* Component uses 334 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 3.14 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 403 logical lines of code
* Class has 527 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
App\Traits\Stripe\StripeInvoice
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=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Blob / God object Probably bugged
App\Traits\Stripe\StripeConnectAccount
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=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Blob / God object Probably bugged
App\Traits\TransferPayoutReport
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.18 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Repositories\MemberRepo
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 243)
* Component uses 883 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 9.73 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 1032 logical lines of code
* Class has 1227 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
App\Repositories\UserRepo
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Models\Transaction\traits\Scopes
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
App\Models\Location\traits\Scopes
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Models\Member\traits\Scopes
Probably bugged warning
This component contains in theory 0.37 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
App\Models\Member\Member
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=12)
* 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 111)
* Component uses 369 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 42)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.42 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 491 logical lines of code
* Class has 640 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 22, so this class uses 22 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
App\Models\User\UserLogin
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=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.45 bugs.

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

Maybe you should check your unit tests for this class.
Blob / God object Probably bugged
App\Exports\AdminExportPayoutReport
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.94 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Exports\InvoicesExport
Probably bugged warning
This component contains in theory 0.75 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
App\Exports\PartnerMemberTransactionExport
Probably bugged warning
This component contains in theory 1.22 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 0 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 233 logical lines of code
* Class has 298 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
App\Exports\CommissionsAnalysisExport
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
* 0 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 245 logical lines of code
* Class has 435 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
App\Utilities\Constant
Probably bugged warning
This component contains in theory 1.63 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
App\Utilities\StaticSeederPermission
Probably bugged warning
This component contains in theory 1.03 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
App\Http\Middleware\OnBoardingProcess
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
App\Http\Responses\LoginResponse
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
App\Http\Controllers\ReportingController
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 81)
* Component uses 337 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 3.36 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 375 logical lines of code
* Class has 433 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
App\Http\Controllers\LocationController
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=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 108)
* Component uses 310 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 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
* 0 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 410 logical lines of code
* Class has 508 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.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
App\Http\Controllers\TransferPayoutController
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 76)
* Component uses 315 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 2.9 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 332 logical lines of code
* Class has 338 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
App\Http\Controllers\Plan\PlanController
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=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 71)
* Component uses 205 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 2.22 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 255 logical lines of code
* Class has 327 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
App\Http\Controllers\MarketingController
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.
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.11 bugs.

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

Maybe you should check your unit tests for this class.
Blob / God object Too complex method code Probably bugged
App\Http\Controllers\User\AdminController
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too dependent information
This class looks use really high number of components.

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Probably bugged Too dependent
App\Http\Controllers\User\MemberController
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 281)
* Component uses 977 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 10.97 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 1229 logical lines of code
* Class has 1369 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 37, so this class uses 37 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
App\Http\Controllers\User\AccountSettingController
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Http\Controllers\User\UserManagementController
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.
Probably bugged warning
This component contains in theory 0.63 bugs.

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

Maybe you should check your unit tests for this class.
Blob / God object Probably bugged
App\Http\Controllers\User\GroupController
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 54)
* Component uses 186 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.94 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 280 logical lines of code
* Class has 344 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 22, so this class uses 22 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
App\Http\Controllers\User\MemberRequestWelcomeKitController
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Http\Controllers\User\RegionController
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Http\Controllers\User\PartnerController
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 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
* 0 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 202 logical lines of code
* Class has 255 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
App\Http\Controllers\AjaxController
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=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.
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Blob / God object Probably bugged
App\Http\Controllers\FeeScheduleController
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.68 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Http\Controllers\Api\MemberController
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (22, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=15)
* 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 115)
* Component uses 369 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 20)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.56 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 501 logical lines of code
* Class has 579 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 22, so this class uses 22 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
App\Http\Controllers\Api\ApiController
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=12)
* 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 105)
* Component uses 363 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.74 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 446 logical lines of code
* Class has 468 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.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
App\Http\Controllers\onBoardingController
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.66 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Rules\PlanCommission
Probably bugged warning
This component contains in theory 0.48 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
App\HelperModules\PlanUpgradeHelper
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.41 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\HelperModules\HelperModule
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 5.41 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 777 logical lines of code
* Class has 912 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 27, so this class uses 27 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
App\HelperModules\StripeFieldsHelper
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 1.32 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Jobs\Refund
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
App\Jobs\PaymentIntent
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 165)
* 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 35)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 5.36 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 687 logical lines of code
* Class has 835 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
App\Jobs\WebHookScheduler
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.4 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Jobs\SubscriptionDelete
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
App\Jobs\TurnOffLocation
Probably bugged warning
This component contains in theory 0.6 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
App\Jobs\ExportCSV
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 101)
* Component uses 211 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 2.31 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 214 logical lines of code
* Class has 232 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
App\Jobs\ScheduleExportMembers
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 78)
* Component uses 165 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.67 bugs.

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

Maybe you should check your unit tests for this class.
Too complex class code Too complex method code Probably bugged
App\Jobs\DisputeCreate
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Jobs\CheckAndCorrectMissingCommission
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.49 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Jobs\SubscriptionRenewal
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
App\Jobs\ScheduleExportTransferPayouts
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.78 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Jobs\InvoicePaid
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 174)
* Component uses 524 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 43)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 5.94 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 748 logical lines of code
* Class has 897 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 20, so this class uses 20 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
App\Listeners\PersonAddressModifiedListener
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
App\Services\PlanUpgradeService
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.77 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Services\EmailService
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 135)
* Component uses 376 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 68)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.32 bugs.

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

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 352 logical lines of code
* Class has 406 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
App\Console\Commands\SwitchMemberPlan
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.43 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Console\Commands\OverDueEmailCommand
Probably bugged warning
This component contains in theory 0.52 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
App\Console\Commands\WebhookReQueue
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.
Too complex method code
App\Console\Commands\LocationPricePlanChange
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.45 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
App\Console\Commands\SanitizeDatabaseForDevelopment
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
App\Console\Kernel
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
* 0 testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged

Package Violations

Package Violations
App\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
App\Traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Traits\Stripe
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\WebHook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Note\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Transaction
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Transaction\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Group
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.115) than 1 package(s) that it depends on.
The packages that are more stable are

* App\Models\Group\traits (0.857)
Stable Abstractions Principle Stable Dependencies Principle
App\Models\Group\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Person\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Person
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Plan\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Plan
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Location\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Location
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.094) than 1 package(s) that it depends on.
The packages that are more stable are

* App\Models\Location\traits (0.875)
Stable Abstractions Principle Stable Dependencies Principle
App\Models\PlanLocation
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Constants
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Member\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Member
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.48) than 2 package(s) that it depends on.
The packages that are more stable are

* App\Repositories (0.824)
* App\Services (0.5)
Stable Abstractions Principle Stable Dependencies Principle
App\Models\User\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\User
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.321) than 1 package(s) that it depends on.
The packages that are more stable are

* App\Services (0.5)
Stable Abstractions Principle Stable Dependencies Principle
App\Models\Subscription
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Subscription\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Partner\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Partner
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.158) than 1 package(s) that it depends on.
The packages that are more stable are

* App\Models\Partner\traits (0.857)
Stable Abstractions Principle Stable Dependencies Principle
App\Models\Price
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\Region
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.143) than 1 package(s) that it depends on.
The packages that are more stable are

* App\Models\Region\traits (0.857)
Stable Abstractions Principle Stable Dependencies Principle
App\Models\Region\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\PaymentGateway\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\PaymentGateway
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Models\ActivityLog\traits
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Utilities
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
App\Http\Controllers
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* App\Exports (0.853)
* App\Jobs (0.833)
Stable Dependencies Principle
App\HelperModules
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.284) than 4 package(s) that it depends on.
The packages that are more stable are

* App\Models\User (0.321)
* App\Models\ActivityLog (0.5)
* App\Models\PaymentGateway (0.294)
* App\Models\Member (0.48)
Stable Abstractions Principle Stable Dependencies Principle
App\Jobs
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* App\Mail (0.833)
* App\Exports (0.853)
Stable Dependencies Principle
App\Events
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 1 package(s) that it depends on.
The packages that are more stable are

* App\Models\Member (0.48)
Stable Abstractions Principle Stable Dependencies Principle
App\Services
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

* App\Repositories (0.824)
Stable Dependencies Principle