Created at 2019-03-21 03:52:01 , with PHPMetrics v2.4.1 (Jean-François Lépine).
Violations
1759
Information
304
Warnings
589
Errors
866
Criticals
0

Class Violations

Class Violations
GitInfo
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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.
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 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 222 logical lines of code
* Class has 339 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
ContentSecurityPolicy
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 69)
* Component uses 175 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 1.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 251 logical lines of code
* Class has 431 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
MediaWiki\Widget\DateInputWidget
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
MediaWiki\Widget\Search\SearchFormWidget
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\Widget\Search\FullSearchResultWidget
Probably bugged warning
This component contains in theory 0.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.
Probably bugged
MediaWiki\Widget\Search\InterwikiSearchResultSetWidget
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
MediaWiki\Widget\Search\BasicSearchResultSetWidget
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
MediaWiki\Widget\CheckMatrixWidget
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.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
SearchSuggestionSet
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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.
Blob / God object
SearchNearMatcher
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.
Too complex method code
SearchHighlighter
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 72)
* Component uses 295 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.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 360 logical lines of code
* Class has 497 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
SearchEngine
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 421 logical lines of code
* Class has 828 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
SearchMssql
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.
Probably bugged
SearchPostgres
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
SearchOracle
Probably bugged warning
This component contains in theory 0.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.
Probably bugged
SearchMySQL
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.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 234 logical lines of code
* Class has 364 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
SearchSqlite
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.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
Preferences
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (20, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=21)
* 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
WebRequest
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (57, 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 119)
* Component uses 345 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 2.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 657 logical lines of code
* Class has 1238 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
ActorMigration
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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 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.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.
Blob / God object Too complex method code Probably bugged
WatchedItemStore
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 89)
* Component uses 286 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 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.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 577 logical lines of code
* Class has 892 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.
Too complex class code Too complex method code Probably bugged Too long Too dependent
WatchedItemQueryService
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 386 logical lines of code
* Class has 497 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
NoWriteWatchedItemStore
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (25, 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.
Blob / God object
LinkFilter
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 47)
* Component uses 172 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.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 200 logical lines of code
* Class has 331 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
TemplateParser
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
EtcdConfig
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.
Probably bugged
PageDataRequestHandler
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
MergeHistory
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
SiteStats
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
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.
Blob / God object Probably bugged
Html
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (28, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=30)
* 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 258 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 2.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 463 logical lines of code
* Class has 921 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
StreamFile
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
Message
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (43, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=13)
* 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 109)
* Component uses 332 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 2.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 569 logical lines of code
* Class has 1290 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
TableDiffFormatter
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
DiffFormatter
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.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
DiffEngine
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 162)
* Component uses 665 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 4.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 488 logical lines of code
* Class has 645 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
TextSlotDiffRenderer
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
DifferenceEngine
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 215)
* Component uses 644 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 45)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 6.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 long information
This class looks really long.

* Class has 916 logical lines of code
* Class has 1519 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
Autopromote
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.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
MagicWordFactory
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.
Probably bugged
FormOptions
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 32)
* Component uses 75 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 11)

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 class code Too complex method code Probably bugged
MediaWiki\Storage\PageUpdater
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 60)
* Component uses 221 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.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 484 logical lines of code
* Class has 1039 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
MediaWiki\Storage\NameTableStore
Probably bugged warning
This component contains in theory 0.74 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\Storage\SqlBlobStore
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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

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

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

* Class has 244 logical lines of code
* Class has 501 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
MediaWiki\Storage\RevisionSlotsUpdate
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (14, 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
MediaWiki\Storage\DerivedPageDataUpdater
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 145)
* Component uses 379 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.15 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 660 logical lines of code
* Class has 1231 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
MediaWiki\Logger\LegacyLogger
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 67)
* Component uses 177 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 1.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 234 logical lines of code
* Class has 386 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
MediaWiki\Logger\Monolog\KafkaHandler
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
MWDebug
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* Component uses 136 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 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
* 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 431 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
DummyLinker
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (49, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=49)
* 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
* 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 200 logical lines of code
* Class has 203 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
CategoryFinder
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.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
DatabaseLogEntry
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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.
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.
Blob / God object Probably bugged
ManualLogEntry
Too complex class code error
This class looks really complex.

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

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 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 244 logical lines of code
* Class has 419 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
LogFormatter
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (16, 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 110)
* Component uses 253 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 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 534 logical lines of code
* Class has 775 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.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
LogPager
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
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
* 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 283 logical lines of code
* Class has 433 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
LogPage
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (14, 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 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 225 logical lines of code
* Class has 374 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
ProtectLogFormatter
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
* testsuites has dependency to this class.

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

* Algorithms are complex (Total cyclomatic complexity of class is 48)
* Component uses 125 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.11 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
BlockLogFormatter
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 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
LogEventsList
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 83)
* Component uses 269 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.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.
Too long information
This class looks really long.

* Class has 379 logical lines of code
* Class has 584 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
RightsLogFormatter
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.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 complex method code Probably bugged
WikiFilePage
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
ImageHistoryList
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 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 complex method code Probably bugged
ImageHistoryPseudoPager
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.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
Article
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (106, 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 231)
* Component uses 723 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 8.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 1319 logical lines of code
* Class has 2221 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 51, so this class uses 51 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
PageArchive
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (15, 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 63)
* Component uses 236 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.15 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 381 logical lines of code
* Class has 609 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
ImagePage
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (12, 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 128)
* 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 38)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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 635 logical lines of code
* Class has 904 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
WikiPage
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (89, 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 308)
* Component uses 933 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 10.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 1658 logical lines of code
* Class has 3024 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 59, so this class uses 59 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
EmailNotification
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 63)
* Component uses 153 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.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 211 logical lines of code
* Class has 362 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
UserMailer
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
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 256 logical lines of code
* Class has 458 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
CategoryViewer
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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 64)
* Component uses 274 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.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 long information
This class looks really long.

* Class has 369 logical lines of code
* Class has 570 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
OrderedStreamingForkController
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.
Probably bugged
MagicWord
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (27, 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.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.
Too long information
This class looks really long.

* Class has 208 logical lines of code
* Class has 458 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
MediaWiki\Site\MediaWikiPageNameNormalizer
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.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
SiteImporter
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
Site
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (26, 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 27)
* Component uses 84 operators

Maybe you should delegate some code to other objects.
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 long information
This class looks really long.

* Class has 248 logical lines of code
* Class has 647 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
DBSiteStore
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.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.
Too complex method code Probably bugged
OldChangesList
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.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
EnhancedChangesList
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 96)
* Component uses 352 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 3.33 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 449 logical lines of code
* Class has 625 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
ChangesFeed
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.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 complex method code Probably bugged
ChangesListFilter
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
RecentChange
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (29, 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 111)
* Component uses 272 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.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 550 logical lines of code
* Class has 934 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
ChangesList
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (28, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=13)
* 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 64)
* Component uses 258 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 2.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.
Too long information
This class looks really long.

* Class has 404 logical lines of code
* Class has 652 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 Probably bugged Too long Too dependent
ChangesListFilterGroup
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
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 Probably bugged
RCCacheEntryFactory
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
MediaWiki\Linker\LinkRenderer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 44)
* Component uses 154 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 236 logical lines of code
* Class has 385 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
MediaWiki
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (10, 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 154)
* Component uses 384 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 3.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 599 logical lines of code
* Class has 895 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 39, so this class uses 39 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
FormatJson
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.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
Xml
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (35, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=36)
* 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 60)
* Component uses 242 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 2.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 392 logical lines of code
* Class has 728 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
MWRestrictions
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (8, 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
AutoloadGenerator
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
ClassCollector
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.
Too complex method code
ZipDirectoryReader
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 63)
* Component uses 277 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 2.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 338 logical lines of code
* Class has 570 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
UIDGenerator
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 46)
* Component uses 241 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 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 347 logical lines of code
* Class has 653 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
AvroValidator
Too complex method code error
This class looks really complex.

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

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
BatchRowIterator
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
DatabaseOracle
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (57, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=26)
* 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 182)
* Component uses 627 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 6.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 942 logical lines of code
* Class has 1116 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
MWLBFactory
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 0.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.
Too complex method code Probably bugged
ApiPageSet
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 164)
* Component uses 414 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 3.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 858 logical lines of code
* Class has 1323 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
ApiQueryFilearchive
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 1.23 bugs.

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

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

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 319 logical lines of code
* Class has 349 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
ApiMain
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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 224)
* Component uses 638 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 7.32 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 1125 logical lines of code
* Class has 1647 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.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
ApiQueryLangLinks
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.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
ApiResult
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (34, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=21)
* 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 169)
* Component uses 351 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.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 600 logical lines of code
* Class has 1081 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
ApiQueryRevisions
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 82)
* Component uses 238 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 78)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 299 logical lines of code
* Class has 355 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
ApiTag
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.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 complex method code Probably bugged
ApiRevisionDelete
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.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
ApiQueryDeletedRevisions
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 1.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 complex method code Probably bugged
ApiErrorFormatter
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (11, 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.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.
Blob / God object Probably bugged
ApiErrorFormatter_BackCompat
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
ApiQueryImages
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.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.
Too complex method code Probably bugged
ApiRollback
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
ApiImageRotate
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.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
ApiQueryAllDeletedRevisions
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 69)
* Component uses 195 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 2.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 292 logical lines of code
* Class has 328 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
ApiUndelete
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
ApiQueryLinks
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.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 complex method code Probably bugged
ApiQueryExternalLinks
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.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 complex method code Probably bugged
ApiQueryQueryPage
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.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
ApiQuerySiteinfo
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (15, 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 122)
* Component uses 382 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.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.
Too long information
This class looks really long.

* Class has 679 logical lines of code
* Class has 707 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
ApiQueryContributors
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.89 bugs.

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

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

* object has lot of public methods (12, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=13)
* 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 112)
* Component uses 287 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 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
* 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 453 logical lines of code
* Class has 597 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
ApiAMCreateAccount
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (9, 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
ApiQueryAllLinks
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.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 complex method code Probably bugged
ApiQueryAllCategories
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.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 complex method code Probably bugged
ApiFeedContributions
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.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 complex method code Probably bugged
ApiMove
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.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 method code Probably bugged
ApiQueryWatchlist
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 92)
* Component uses 210 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 1.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.
Too long information
This class looks really long.

* Class has 291 logical lines of code
* Class has 316 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
ApiQueryIWLinks
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.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
ApiQueryBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (13, 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.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 47)
* Component uses 140 operators

Maybe you should delegate some code to other objects.
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 275 logical lines of code
* Class has 551 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
ApiFormatBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (12, 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 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.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.
Blob / God object Too complex method code Probably bugged
ApiHelp
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (8, 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 141)
* Component uses 387 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 116)

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 544 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 20, so this class uses 20 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
ApiMergeHistory
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
ApiQueryRecentChanges
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (10, 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 144)
* Component uses 296 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 82)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.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 long information
This class looks really long.

* Class has 433 logical lines of code
* Class has 510 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
ApiLogin
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 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 method code Probably bugged
ApiQueryAllImages
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
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 213 logical lines of code
* Class has 250 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
ApiQueryLangBacklinks
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.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 complex method code Probably bugged
ApiQueryAllMessages
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 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.
Too complex method code Probably bugged
ApiQueryUserContribs
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.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 405 logical lines of code
* Class has 461 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
ApiQueryUsers
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 57)
* Component uses 136 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 53)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 long information
This class looks really long.

* Class has 267 logical lines of code
* Class has 321 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
ApiQueryCategoryMembers
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 1.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 long information
This class looks really long.

* Class has 212 logical lines of code
* Class has 275 lines of code

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

Maybe you should check your unit tests for this class.
Probably bugged
ApiImport
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.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 complex method code Probably bugged
ApiModuleManager
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
ApiQueryBacklinksprop
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 266 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
ApiQueryBacklinks
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 76)
* Component uses 231 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.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.
Too long information
This class looks really long.

* Class has 334 logical lines of code
* Class has 419 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
ApiLinkAccount
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (9, 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
ApiExpandTemplates
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.63 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
ApiAuthManagerHelper
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (10, 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 41)
* Component uses 114 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 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.
Too long information
This class looks really long.

* Class has 204 logical lines of code
* Class has 279 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
ApiStashEdit
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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 45)
* Component uses 152 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 1.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 long information
This class looks really long.

* Class has 260 logical lines of code
* Class has 382 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
ApiQueryDuplicateFiles
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.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
ApiParse
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 147)
* Component uses 362 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 3.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 552 logical lines of code
* Class has 643 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
ApiBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (55, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=16)
* 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 320)
* Component uses 702 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 103)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 7.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 1267 logical lines of code
* Class has 2275 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 28, so this class uses 28 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
ApiFormatXml
Too complex class code error
This class looks really complex.

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

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 class code Too complex method code Probably bugged
ApiUnblock
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
ApiQueryCategories
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.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
ApiBlock
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 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
ApiQueryRevisionsBase
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 long information
This class looks really long.

* Class has 406 logical lines of code
* Class has 481 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
ApiComparePages
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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.
Too long information
This class looks really long.

* Class has 450 logical lines of code
* Class has 531 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
ApiQuery
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 51)
* Component uses 121 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.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 257 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
ApiQueryAllRevisions
Too complex method code error
This class looks really complex.

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

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 complex method code Probably bugged
ApiQueryRandom
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.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
ApiQueryPagesWithProp
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.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 complex method code Probably bugged
ApiOpenSearch
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.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 227 logical lines of code
* Class has 280 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
ApiQueryLogEvents
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 73)
* Component uses 180 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.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 complex class code Too complex method code Probably bugged
ApiClientLogin
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (8, 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
ApiParamInfo
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 118)
* Component uses 255 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 2.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 427 logical lines of code
* Class has 473 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
ApiQueryExtLinksUsage
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
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 0.83 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 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
ApiQueryIWBacklinks
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.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 complex method code Probably bugged
ApiQueryProtectedTitles
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 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.
Too complex method code Probably bugged
ApiDelete
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.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 complex method code Probably bugged
ApiQueryAllPages
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 45)
* Component uses 98 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 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 complex class code Too complex method code Probably bugged
ApiUserrights
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
* testsuites has dependency to this class.

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

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* Component uses 152 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.87 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 233 logical lines of code
* Class has 257 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
ApiEditPage
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 347 logical lines of code
* Class has 433 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
ApiQuerySearch
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 58)
* Component uses 149 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 34)

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

* Class has 259 logical lines of code
* Class has 320 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
ApiQueryAllUsers
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 207 logical lines of code
* Class has 261 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
ApiQueryTags
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
* testsuites has dependency to this class.

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

* object has lot of public methods (17, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=16)
* 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 132)
* Component uses 355 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 3.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 635 logical lines of code
* Class has 762 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
ApiWatch
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
ApiUpload
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 519 logical lines of code
* Class has 712 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
ApiProtect
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.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.
Too complex method code Probably bugged
ApiFeedWatchlist
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.11 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
ApiMessageTrait
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
ApiCSPReport
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
ApiQueryUserInfo
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 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 long information
This class looks really long.

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

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
ApiQueryWatchlistRaw
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.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 method code Probably bugged
Linker
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (49, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=53)
* 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 273)
* Component uses 869 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 8.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 1045 logical lines of code
* Class has 1789 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
MWTimestamp
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
Status
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 0.83 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 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 205 logical lines of code
* Class has 380 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
Revision
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 long information
This class looks really long.

* Class has 522 logical lines of code
* Class has 1146 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
ProtectionForm
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 307 logical lines of code
* Class has 419 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
SiteConfiguration
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 81)
* Component uses 155 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.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 272 logical lines of code
* Class has 543 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
ForkController
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
MediaWiki\Interwiki\ClassicInterwikiLookup
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 46)
* Component uses 147 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 12)

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

* Class has 218 logical lines of code
* Class has 353 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
BaseDump
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
WikiExporter
Too complex class code error
This class looks really complex.

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

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 269 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
XmlDumpWriter
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (18, 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 45)
* Component uses 261 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 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.
Too long information
This class looks really long.

* Class has 260 logical lines of code
* Class has 405 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
SiteStatsInit
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
TrackingCategories
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
PasswordFactory
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
UserPasswordPolicy
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.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 complex method code Probably bugged
JSMinPlus
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 160)
* Component uses 362 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 155)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 455 logical lines of code
* Class has 472 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
JSParser
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 263)
* Component uses 419 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 138)

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
* 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 782 logical lines of code
* Class has 827 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
JSTokenizer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 88)
* Component uses 175 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 79)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 class code Too complex method code Probably bugged
Cookie
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.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
ParsoidVirtualRESTService
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
VirtualRESTServiceClient
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.72 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
RestbaseVirtualRESTService
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.
Probably bugged
SwiftVirtualRESTService
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
IEUrlExtension
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
JavaScriptMinifier
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 74)
* Component uses 199 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 1.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 313 logical lines of code
* Class has 538 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
Wikimedia\Rdbms\DatabaseDomain
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.
Probably bugged
Wikimedia\Rdbms\Database
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (154, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=43)
* 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 558)
* Component uses 1581 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.78 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 2821 logical lines of code
* Class has 4009 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 28, so this class uses 28 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
Wikimedia\Rdbms\DatabaseSqlite
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (54, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=34)
* 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 101)
* Component uses 347 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 3.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 645 logical lines of code
* Class has 987 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
Wikimedia\Rdbms\DatabasePostgres
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (69, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=25)
* 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 147)
* Component uses 542 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 5.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 951 logical lines of code
* Class has 1194 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
Wikimedia\Rdbms\DatabaseMysqlBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (52, 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 151)
* Component uses 485 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.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.
Too long information
This class looks really long.

* Class has 819 logical lines of code
* Class has 1327 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
Wikimedia\Rdbms\MySQLMasterPos
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 43)
* Component uses 104 operators

Maybe you should delegate some code to other objects.
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.
Blob / God object Too complex class code Probably bugged
Wikimedia\Rdbms\DatabaseMysqli
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
Wikimedia\Rdbms\DBConnRef
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (140, 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 10)
* Component uses 153 operators

Maybe you should delegate some code to other objects.
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 588 logical lines of code
* Class has 614 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
Wikimedia\Rdbms\DatabaseMssql
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (45, 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 137)
* Component uses 477 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 4.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 792 logical lines of code
* Class has 1225 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
Wikimedia\Rdbms\LoadBalancer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 261)
* Component uses 744 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 7.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 1273 logical lines of code
* Class has 1660 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
Wikimedia\Rdbms\ChronologyProtector
Probably bugged warning
This component contains in theory 0.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.
Probably bugged
Wikimedia\Rdbms\TransactionProfiler
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 40)
* Component uses 94 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 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.
Too complex class code Too complex method code Probably bugged
Wikimedia\Rdbms\LoadMonitor
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 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
Wikimedia\Rdbms\LBFactory
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (34, 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 79)
* Component uses 207 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 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 447 logical lines of code
* Class has 601 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
Wikimedia\Rdbms\LBFactoryMulti
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
Wikimedia\Rdbms\LBFactorySingle
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 79)
* Component uses 196 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.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 338 logical lines of code
* Class has 524 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
XhprofData
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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 44)
* Component uses 102 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 0.83 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 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
CSSMin
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=13)
* 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 57)
* Component uses 216 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.75 bugs.

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

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

* Class has 236 logical lines of code
* Class has 454 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
StatusValue
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
StringUtils
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
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.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.
Blob / God object Too complex method code Probably bugged
CryptHKDF
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
XmlTypeCheck
Too complex class code error
This class looks really complex.

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

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

* Class has 252 logical lines of code
* Class has 438 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
IEContentAnalyzer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 134)
* Component uses 339 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 51)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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.
Too long information
This class looks really long.

* Class has 373 logical lines of code
* Class has 518 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
MSCompoundFileReader
Probably bugged warning
This component contains in theory 1.34 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 224 logical lines of code
* Class has 280 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
MimeAnalyzer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 155)
* Component uses 445 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 4.33 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 728 logical lines of code
* Class has 1071 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
Wikimedia\Services\ServiceContainer
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
LockManager
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
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
RedisLockManager
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
MemcLockManager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 44)
* Component uses 93 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 0.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 203 logical lines of code
* Class has 305 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
QuorumLockManager
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.
Probably bugged
FSLockManager
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
RiffExtractor
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
IP
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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
* 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 392 logical lines of code
* Class has 688 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
HTTPFileStreamer
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.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.
Too complex method code Probably bugged
MemoryFileBackend
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
FSFileBackend
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 127)
* Component uses 331 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 3.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 566 logical lines of code
* Class has 769 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
SwiftFileBackend
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (10, 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 233)
* Component uses 738 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 8.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 1077 logical lines of code
* Class has 1548 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
FileBackend
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 390 logical lines of code
* Class has 1522 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
FileBackendStore
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (35, 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 199)
* Component uses 626 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 6.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 long information
This class looks really long.

* Class has 1040 logical lines of code
* Class has 1794 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
FileOpBatch
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.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 complex method code Probably bugged
FileBackendMultiWrite
Too complex class code error
This class looks really complex.

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

* Class has 486 logical lines of code
* Class has 712 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
FileOp
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 38)
* Component uses 106 operators

Maybe you should delegate some code to other objects.
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
* 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 242 logical lines of code
* Class has 430 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
HashRing
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 38)
* Component uses 145 operators

Maybe you should delegate some code to other objects.
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 229 logical lines of code
* Class has 390 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
RedisConnRef
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
RedisConnectionPool
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

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

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

* Class has 204 logical lines of code
* Class has 338 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
MWMessagePack
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 0.68 bugs.

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

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

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

Maybe you should delegate some code to other objects.
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
* testsuites has dependency to this class.

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

* object has lot of public methods (19, 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 47)
* Component uses 160 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 1.27 bugs.

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

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

* Class has 274 logical lines of code
* Class has 377 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
BitmapMetadataHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
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.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.
Blob / God object Too complex method code Probably bugged
GIFMetadataExtractor
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.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 complex method code Probably bugged
MediaHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (52, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=51)
* 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 24)
* Component uses 127 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 1.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 301 logical lines of code
* Class has 860 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
SVGReader
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 234 logical lines of code
* Class has 324 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
FormatMetadata
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 493)
* Component uses 612 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 361)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 6.88 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 1226 logical lines of code
* Class has 1640 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
TransformationalImageHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (12, 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 60)
* Component uses 177 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 1.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.
Too long information
This class looks really long.

* Class has 265 logical lines of code
* Class has 518 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
BitmapHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability 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 89)
* Component uses 249 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 2.63 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 367 logical lines of code
* Class has 526 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
IPTC
Too complex class code error
This class looks really complex.

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

* Class has 374 logical lines of code
* Class has 586 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
GIFHandler
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
* testsuites has dependency to this class.

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

* Algorithms are complex (Total cyclomatic complexity of class is 84)
* Component uses 216 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.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.
Too long information
This class looks really long.

* Class has 502 logical lines of code
* Class has 874 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
ImageHandler
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.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
JpegHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (9, 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 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.
Blob / God object Probably bugged
WebPHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (13, 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.
Probably bugged warning
This component contains in theory 0.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.
Blob / God object Probably bugged
SvgHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (25, 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 71)
* Component uses 224 operators

Maybe you should delegate some code to other objects.
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 379 logical lines of code
* Class has 536 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
DjVuImage
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 193 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 11)

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
* 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 264 logical lines of code
* Class has 346 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
JpegMetadataExtractor
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.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
MediaTransformOutput
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
ThumbnailImage
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.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.