Created at 2020-07-04 03:53:47 , with PHPMetrics v2.4.1 (Jean-François Lépine).
Violations
1905
Information
320
Warnings
669
Errors
916
Criticals
0

Class Violations

Class Violations
LanguageTyv
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 67)
* Component uses 138 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

Maybe you should check your unit tests for this class.
Too complex class code Too complex method code Probably bugged
LanguageFi
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.48 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
LanguageOs
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.
Too complex method code
LanguageKsh
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.47 bugs.

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

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

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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 654 logical lines of code
* Class has 768 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
LanguageWa
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.36 bugs.

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

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

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

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
Language
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (157, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=48)
* 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 557)
* Component uses 2022 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 132)

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

* object has lot of public methods (23, 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 143)
* Component uses 457 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 4.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 672 logical lines of code
* Class has 1120 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\Languages\Data\ZhConversion
Probably bugged warning
This component contains in theory 202.99 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\Languages\Data\Names
Probably bugged warning
This component contains in theory 2.93 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://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 607 logical lines of code
* Class has 925 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
MediaWiki\Languages\Data\CrhExceptions
Probably bugged warning
This component contains in theory 11.59 bugs.

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

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

* Class has 1043 logical lines of code
* Class has 1168 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
RunJobs
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.
Too complex method code
InitEditCount
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
UserOptionsMaintenance
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.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
CleanupInvalidDbKeys
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.93 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://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
RebuildLocalisationCache
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.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
NamespaceDupes
Too complex class code error
This class looks really complex.

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

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

* Class has 329 logical lines of code
* Class has 498 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
GenerateSitemap
Too complex class code error
This class looks really complex.

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

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 240 logical lines of code
* Class has 436 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
TitleCleanup
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.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
MigrateFileRepoLayout
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.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
UpdateExtensionJsonSchema
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.
Probably bugged
RecompressTracked
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=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 67)
* Component uses 205 operators

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

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

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

* Class has 431 logical lines of code
* Class has 541 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
CheckStorage
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 71)
* Component uses 190 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 357 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 Too complex method code Probably bugged Too long
CompressOld
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.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 230 logical lines of code
* Class has 317 lines of code

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

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

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

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
CreateAndPromote
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.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
RebuildFileCache
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.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
BenchmarkTidy
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
BenchmarkSanitizer
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
BenchIfSwitch
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
BenchmarkParse
Probably bugged warning
This component contains in theory 0.43 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
PopulateChangeTagDef
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
UserDupes
Probably bugged warning
This component contains in theory 0.61 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 60)
* Component uses 139 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.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 242 logical lines of code
* Class has 285 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
CheckDependencies
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.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
MwSql
Too complex method code error
This class looks really complex.

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
PopulateContentTables
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 207 logical lines of code
* Class has 255 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
GetConfiguration
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.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
CleanupUploadStash
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.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
CleanupSpam
Too complex method code error
This class looks really complex.

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

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

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

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

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

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 270 logical lines of code
* Class has 369 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
CreateCommonPasswordCdb
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
RecountCategories
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
CleanupImages
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.
Probably bugged
DumpIterator
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
AddSite
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
TableCleanup
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.
Probably bugged
ResetAuthenticationThrottle
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
EraseArchivedFile
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
BackupReader
Too complex class code error
This class looks really complex.

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

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

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://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 243 logical lines of code
* Class has 279 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
Orphans
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.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 complex method code Probably bugged
FindOrphanedFiles
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
MWDocGen
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
GenerateJsonI18n
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.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
RebuildRecentchanges
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 255 logical lines of code
* Class has 317 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
CleanupEmptyCategories
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.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
PopulateIpChanges
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
MoveBatch
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
CopyFileBackend
Too complex class code error
This class looks really complex.

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

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 243 logical lines of code
* Class has 323 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
MigrateArchiveText
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.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
MigrateComments
Probably bugged warning
This component contains in theory 0.97 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
FindMissingFiles
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.36 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
UpdateCollation
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.25 bugs.

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

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

* Class has 218 logical lines of code
* Class has 236 lines of code

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

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
DumpBackup
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
FixTimestamps
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
FixDoubleRedirects
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.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
PopulateLogSearch
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.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
RemoveUnusedAccounts
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.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 complex method code Probably bugged
PurgeChangedFiles
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.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 complex method code Probably bugged
RefreshFileHeaders
Too complex method code error
This class looks really complex.

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
PurgeList
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
UpdateLogging
Probably bugged warning
This component contains in theory 0.55 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
InvalidateUserSesssions
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
CleanupCaps
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
MergeMessageFileList
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.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
UpdateMediaWiki
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.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 method code Probably bugged
CleanupUsersWithNoId
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.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
CommandLineInstaller
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
ImportImages
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 289 logical lines of code
* Class has 342 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
DeduplicateArchiveRevId
Too complex method code error
This class looks really complex.

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
FindHooks
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.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 202 logical lines of code
* Class has 259 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
CleanupBlocks
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.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
DeleteArchivedFiles
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
FindBadBlobs
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 44)
* Component uses 164 operators

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

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

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

* Class has 266 logical lines of code
* Class has 367 lines of code

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

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

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

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

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

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

* Class has 345 logical lines of code
* Class has 529 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
DeleteBatch
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
ImportTextFiles
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.69 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 90)
* Component uses 262 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.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 399 logical lines of code
* Class has 504 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
ReassignEdits
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.
Probably bugged
PopulateRevisionLength
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
PopulateImageSha1
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.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
DeleteEqualMessages
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.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
WrapOldPasswords
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
DumpCategoriesAsRdf
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
GenerateNormalizerDataAr
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
GenerateCollationData
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* Component uses 150 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.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 203 logical lines of code
* Class has 244 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
ImageBuilder
Probably bugged warning
This component contains in theory 0.62 bugs.

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

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

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

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

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

* Class has 299 logical lines of code
* Class has 382 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
MigrateActors
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.59 bugs.

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

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

* Class has 309 logical lines of code
* Class has 391 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
Benchmarker
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
TextPassDumper
Too complex class code error
This class looks really complex.

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

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

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

* Class has 675 logical lines of code
* Class has 849 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
DeleteLocalPasswords
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
MWDoxygenFilter
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
Maintenance
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=12)
* object knows everything (and use lot of external classes)

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

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

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

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

* Class has 908 logical lines of code
* Class has 1498 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
EditCLI
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.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
PurgeChangedPages
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.48 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
BlockUsers
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
SyncFileBackend
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.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 202 logical lines of code
* Class has 266 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
ShowJobs
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
RefreshImageMetadata
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.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 complex method code Probably bugged
ConvertLinks
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.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 complex method code Probably bugged
RebuildTextIndex
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
PopulateRevisionSha1
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
DeleteAutoPatrolLogs
Probably bugged warning
This component contains in theory 0.45 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 191 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
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.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.
Blob / God object Too complex method code Probably bugged
TransformationalImageHandler
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=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 179 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.54 bugs.

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

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

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

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

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

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

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

* Class has 1236 logical lines of code
* Class has 1660 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
DjVuHandler
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=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 379 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
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.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 Probably bugged
GIFHandler
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
ThumbnailImage
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.61 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ExifBitmapHandler
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.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
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
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.59 bugs.

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

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

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

* object has lot of public methods (24, 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 223 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 376 logical lines of code
* Class has 533 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
MediaHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (51, 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 0.99 bugs.

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

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

* Class has 301 logical lines of code
* Class has 866 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
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
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
PNGMetadataExtractor
Too complex class code error
This class looks really complex.

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

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 277 logical lines of code
* Class has 371 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
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.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
DiffHistoryBlob
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.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 232 logical lines of code
* Class has 337 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
FileDeleteForm
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.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 211 logical lines of code
* Class has 318 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 26, so this class uses 26 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex method code Probably bugged Too long Too dependent
MagicWordFactory
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
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
MediaWiki\Storage\DerivedPageDataUpdater
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

* Class has 660 logical lines of code
* Class has 1254 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

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

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\Storage\PageUpdater
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 69)
* Component uses 248 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.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 522 logical lines of code
* Class has 1100 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

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

Maybe you should check why this class has lot of dependencies.
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.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 205 logical lines of code
* Class has 386 lines of code

Maybe your class should not exceed 200 lines of logical 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\SqlBlobStore
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 54)
* Component uses 171 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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 304 logical lines of code
* Class has 585 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\PageEditStash
Too complex method code error
This class looks really complex.

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

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

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
PoolWorkArticleView
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.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
PoolCounterWork
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
PoolCounterRedis
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.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 278 logical lines of code
* Class has 373 lines of code

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

* Algorithms are complex (Total cyclomatic complexity of class is 235)
* Component uses 471 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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 659 logical lines of code
* Class has 1251 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
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=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 48)
* Component uses 141 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 223 logical lines of code
* Class has 362 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
Pingback
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
MagicWord
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
MagicWordArray
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 37)
* Component uses 130 operators

Maybe you should delegate some code to other objects.
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 class code Probably bugged
TablePager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 25)
* Component uses 124 operators

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

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
IndexPager
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.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 62)
* Component uses 225 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 54)
* Component uses 170 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.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 258 logical lines of code
* Class has 460 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
EmailNotification
Too complex class code error
This class looks really complex.

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

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 211 logical lines of code
* Class has 367 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\LegacyLogger
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 70)
* Component uses 184 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.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 250 logical lines of code
* Class has 422 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\LineFormatter
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
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 (19, 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 57)
* Component uses 154 operators

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

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

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

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

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

* object has lot of public methods (58, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=22)
* 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 246)
* Component uses 827 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 9.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 1233 logical lines of code
* Class has 1936 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 23, so this class uses 23 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
MediaWiki\Tidy\RemexCompatMunger
Too complex class code error
This class looks really complex.

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

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

* Class has 332 logical lines of code
* Class has 459 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\Tidy\RemexCompatFormatter
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 148 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 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 220 logical lines of code
* Class has 357 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\Session\Session
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 33)
* Component uses 134 operators

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

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

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

* Class has 347 logical lines of code
* Class has 609 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
MediaWiki\Session\SessionInfo
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.
Too complex method code
MediaWiki\Session\CookieSessionProvider
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=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 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 11)

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

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

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

* Class has 227 logical lines of code
* Class has 329 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\Session\UserInfo
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=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
MediaWiki\Session\SessionManager
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=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 138)
* 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 51)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 537 logical lines of code
* Class has 751 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 26, so this class uses 26 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
MediaWiki\Session\SessionProvider
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=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.
Blob / God object
MediaWiki\Session\BotPasswordSessionProvider
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
MediaWiki\Session\SessionBackend
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 597 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\Session\PHPSessionHandler
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 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.
Blob / God object Too complex method code Probably bugged
ContentSecurityPolicy
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 76)
* 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 41)

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 292 logical lines of code
* Class has 503 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
MachineReadableRCFeedFormatter
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.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
IRCColourfulRCFeedFormatter
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.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
MWGrants
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=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
MergeHistory
Probably bugged warning
This component contains in theory 0.82 bugs.

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

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

* object has lot of public methods (42, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=20)
* 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 165)
* Component uses 436 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 4.13 bugs.

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

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

* Class has 804 logical lines of code
* Class has 1292 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 23, so this class uses 23 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
MediaWiki\Block\BlockRestrictionStore
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.
Probably bugged
MediaWiki\Block\BlockManager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 63)
* Component uses 160 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.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 263 logical lines of code
* Class has 486 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
MediaWiki\Block\AbstractBlock
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=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 37)
* Component uses 100 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

* Class has 274 logical lines of code
* Class has 611 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\Block\BlockErrorFormatter
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 (13, 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 41)
* Component uses 112 operators

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

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

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

* Class has 225 logical lines of code
* Class has 400 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
JobQueueFederated
Too complex class code error
This class looks really complex.

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

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

* object has lot of public methods (23, 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 37)
* Component uses 106 operators

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

* Class has 281 logical lines of code
* Class has 693 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Probably bugged Too long
JobQueueGroup
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.
Too complex class code error
This class looks really complex.

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

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 261 logical lines of code
* Class has 414 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
JobQueueRedis
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.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 61)
* Component uses 189 operators

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

* Algorithms are complex (Total cyclomatic complexity of class is 73)
* Component uses 231 operators

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

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

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

* Class has 513 logical lines of code
* Class has 790 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
Job
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 50)
* 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 19)

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

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

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

* Class has 224 logical lines of code
* Class has 375 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
JobRunner
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 363 logical lines of code
* Class has 562 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
DoubleRedirectJob
Too complex method code error
This class looks really complex.

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
CategoryMembershipChangeJob
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
ThumbnailRenderJob
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.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
HTMLCacheUpdateJob
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
RefreshLinksJob
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 213 logical lines of code
* Class has 336 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
RecentChangesUpdateJob
Probably bugged warning
This component contains in theory 0.69 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 60)
* Component uses 222 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.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 310 logical lines of code
* Class has 428 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
UploadFromUrl
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=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.
Blob / God object Probably bugged
UploadBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (48, 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 258)
* Component uses 807 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 7.69 bugs.

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

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

* Class has 1150 logical lines of code
* Class has 1840 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
UploadFromChunks
Probably bugged warning
This component contains in theory 0.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 204 logical lines of code
* Class has 338 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
UploadStash
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.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 230 logical lines of code
* Class has 440 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
ChangeTagsLogItem
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=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.
Blob / God object
ChangeTags
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=37)
* 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 376 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

* Class has 617 logical lines of code
* Class has 1185 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 23, so this class uses 23 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
OutputPage
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (123, 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 283)
* Component uses 938 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 11.17 bugs.

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

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

* Class has 1908 logical lines of code
* Class has 3603 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 45, so this class uses 45 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
MediaWiki\Revision\RevisionArchiveRecord
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.
Blob / God object
MediaWiki\Revision\SlotRecord
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (23, 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 34)
* Component uses 106 operators

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

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

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

* Class has 247 logical lines of code
* Class has 543 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
MediaWiki\Revision\RevisionRenderer
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.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
MediaWiki\Revision\RenderedRevision
Too complex class code error
This class looks really complex.

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

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 class code Too complex method code Probably bugged
MediaWiki\Revision\RevisionRecord
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=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 26)
* Component uses 93 operators

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

* Class has 204 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 Probably bugged Too long
MediaWiki\Revision\RevisionStoreRecord
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=6)
* object knows everything (and use lot of external classes)

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

* object has lot of public methods (38, 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 255)
* Component uses 764 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 9.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 1170 logical lines of code
* Class has 2211 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 45, so this class uses 45 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
MediaWiki\Revision\MainSlotRoleHandler
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
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
SearchPostgres
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
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.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 complex method code Probably bugged
SearchEngine
Blob / God object error
A blob object (or "god class") does not follow the Single responsability principle.

* object has lot of public methods (30, 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 51)
* 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.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 410 logical lines of code
* Class has 795 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
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.25 bugs.

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

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

* Class has 237 logical lines of code
* Class has 367 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
PrefixSearch
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.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 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
MediaWiki\Search\SearchWidgets\SearchFormWidget
Probably bugged warning
This component contains in theory 1.09 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\Search\SearchWidgets\FullSearchResultWidget
Probably bugged warning
This component contains in theory 0.81 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 72)
* Component uses 297 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.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 363 logical lines of code
* Class has 498 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
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.44 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
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.86 bugs.

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

Maybe you should check your unit tests for this class.
Too 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 103 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.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 complex class code Too complex method code Probably bugged
ApiQueryAllRevisions
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.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 complex method code Probably bugged
ApiUpload
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=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 120)
* Component uses 271 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.02 bugs.

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

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

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

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

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

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

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 353 logical lines of code
* Class has 422 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
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 42)
* 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 283 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.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
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.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
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
ApiMessageTrait
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
ApiQueryImageInfo
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 124)
* 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 67)

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 429 logical lines of code
* Class has 560 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
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.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
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=8)
* object knows everything (and use lot of external classes)

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

* Algorithms are complex (Total cyclomatic complexity of class is 80)
* Component uses 233 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

* Class has 299 logical lines of code
* Class has 361 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
ApiQueryLanguageinfo
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.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 complex method code Probably bugged
ApiQueryFilearchive
Too complex class code error
This class looks really complex.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 62)
* Component uses 165 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 47)
* Component uses 117 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.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 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
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
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
ApiQueryBacklinks
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 342 logical lines of code
* Class has 412 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 (20, 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 227)
* Component uses 651 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 148)
* Component uses 398 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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 586 logical lines of code
* Class has 679 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 23, so this class uses 23 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
ApiQueryBase
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=12)
* object knows everything (and use lot of external classes)

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

* Algorithms are complex (Total cyclomatic complexity of class is 45)
* Component uses 124 operators

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

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

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

* Class has 280 logical lines of code
* Class has 603 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
ApiQueryQueryPage
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.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
ApiUserrights
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.48 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
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 24)

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

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

Maybe you should check your unit tests for this class.
Blob / God object Too complex method code Probably bugged
ApiQuerySearch
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

* Class has 252 logical lines of code
* Class has 330 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
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.25 bugs.

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

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

* Class has 227 logical lines of code
* Class has 284 lines of code

Maybe your class should not exceed 200 lines of logical 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
ApiQueryContributors
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.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 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
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.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 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
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=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 123)
* Component uses 350 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.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 614 logical lines of code
* Class has 743 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
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
ApiQueryUserContribs
Too complex class code error
This class looks really complex.

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

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

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://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 423 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\Api\Validator\ApiParamValidator
Too complex class code error
This class looks really complex.

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

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 205 logical lines of code
* Class has 304 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\Api\Validator\SubmoduleDef
Too complex method code error
This class looks really complex.

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

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

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

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 53)
* Component uses 124 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.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 262 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 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 14)

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
ApiParamInfo
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 68)
* Component uses 170 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 46)
* Component uses 135 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 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
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=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 148)
* Component uses 326 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 3.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 454 logical lines of code
* Class has 546 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
ApiQueryWatchlistRaw
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.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
ApiQueryLangBacklinks
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.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
ApiQueryCategoryMembers
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.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 218 logical lines of code
* Class has 281 lines of code

Maybe your class should not exceed 200 lines of logical 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 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
ApiQueryRevisionsBase
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 120)
* Component uses 309 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

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

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

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

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

* Class has 420 logical lines of code
* Class has 511 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
ApiQueryPagesWithProp
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.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
ApiImageRotate
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.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
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
ApiQueryLogEvents
Too complex class code error
This class looks really complex.

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

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

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

* Algorithms are compl