Created at 2024-04-26 15:38:02 , with PHPMetrics v2.8.1 (Jean-François Lépine).
Violations
2185
Information
380
Warnings
809
Errors
996
Criticals
0

Class Violations

Class Violations
RebuildLocalisationCache
Too complex method code error
This class looks really complex.

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

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

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

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

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

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

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

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

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

Maybe you should check your unit tests for this class.
Too complex 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.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
DumpCategoriesAsRdf
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
CleanupImages
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.
Probably bugged
TableCleanup
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
CreateBotPassword
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.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
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
ImportTextFiles
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.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
MysqlMaintenance
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.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
ResetUserEmail
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
CreateAndPromote
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.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
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.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
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.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
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.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
RebuildFileCache
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.57 bugs.

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

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

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

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

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

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

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

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

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

Maybe you should delegate some 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 2.94 bugs.

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

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

* Class has 384 logical lines of code
* Class has 485 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
ConvertExtensionToRegistration
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 244 logical lines of code
* Class has 292 lines of code

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

* Algorithms are complex (Total cyclomatic complexity of class is 51)
* Component uses 102 operators

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

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

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 239 logical lines of code
* Class has 276 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
FindMissingActors
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.
Probably bugged
ResetAuthenticationThrottle
Too complex method code error
This class looks really complex.

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 42)
* Component uses 102 operators

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 36)
* Component uses 156 operators

Maybe you should delegate some 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.37 bugs.

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

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

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

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

Maybe you should delegate some 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.32 bugs.

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

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

* Class has 370 logical lines of code
* Class has 404 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
ResolveStubs
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.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
RecompressTracked
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 2.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 422 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
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.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 205 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
MoveToExternal
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 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 235 logical lines of code
* Class has 248 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.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 234 logical lines of code
* Class has 256 lines of code

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

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

Maybe you should delegate some 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.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 377 logical lines of code
* Class has 548 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
ConvertExtensionsMessagesToTranslationAlias
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
PurgeList
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
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.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 complex method code Probably bugged
CompareParsers
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
GenerateConfigSchema
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.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 complex method code Probably bugged
DumpBackup
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
RebuildRecentchanges
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.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 230 logical lines of code
* Class has 285 lines of code

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

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

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

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

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

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

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

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

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

* Class has 451 logical lines of code
* Class has 686 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
DeleteLocalPasswords
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
TextPassDumper
Too complex class code error
This class looks really complex.

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

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

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

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

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

Maybe you should delegate some code to other objects or split complex method.
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 301 logical lines of code
* Class has 407 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
Benchmarker
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.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
MediaWiki\Maintenance\MaintenanceParameters
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 69)
* Component uses 205 operators

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

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

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

* object has lot of public methods (24, 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 97)
* Component uses 281 operators

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

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

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

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

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

* Class has 633 logical lines of code
* Class has 1250 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
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.74 bugs.

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

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

* Class has 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
DumpIterator
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

Maybe your class should not exceed 200 lines of logical code
Too complex class 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 18)

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

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

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

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
RebuildTextIndex
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
PopulateRevisionSha1
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
GrepPages
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
MWEval
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
RecountCategories
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
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.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
CleanupCaps
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
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.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
PopulateRevisionLength
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
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.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
MigrateBlocks
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.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
PopulateIpChanges
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
CompareLanguageConverterOutput
Probably bugged warning
This component contains in theory 0.85 bugs.

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

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

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

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

* Class has 235 logical lines of code
* Class has 271 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
ImageBuilder
Probably bugged warning
This component contains in theory 0.6 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
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.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
FindBadBlobs
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 242 logical lines of code
* Class has 325 lines of code

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

* Algorithms are complex (Total cyclomatic complexity of class is 65)
* Component uses 183 operators

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 131)
* Component uses 352 operators

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

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

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

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

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

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

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

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

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

Maybe you should delegate some 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.68 bugs.

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

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

* Class has 342 logical lines of code
* Class has 627 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
DeprecationHelper
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\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\LogstashFormatter
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.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
MediaWiki\Logger\LegacyLogger
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 74)
* Component uses 187 operators

Maybe you should delegate some 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.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 258 logical lines of code
* Class has 435 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\MonologSpi
Probably bugged warning
This component contains in theory 0.37 bugs.

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

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

* object has lot of public methods (22, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.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.
Blob / God object Probably bugged
MediaWiki\Request\FauxResponse
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
MediaWiki\Request\PathRouter
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 51)
* Component uses 121 operators

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

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

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

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

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

* Class has 207 logical lines of code
* Class has 381 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\Request\ContentSecurityPolicy
Too complex class code error
This class looks really complex.

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

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

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

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 281 logical lines of code
* Class has 484 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\Request\WebRequest
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 118)
* Component uses 370 operators

Maybe you should delegate some 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.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 653 logical lines of code
* Class has 1381 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\Request\WebResponse
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.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
MediaWiki\Navigation\PagerNavigationBuilder
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.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
MediaWiki\PoolCounter\PoolCounterClient
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
MediaWiki\PoolCounter\PoolCounterRedis
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.63 bugs.

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

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

* Class has 280 logical lines of code
* Class has 374 lines of code

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 127)
* Component uses 354 operators

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

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

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

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

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

* Class has 646 logical lines of code
* Class has 1105 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
CategoryMembershipChange
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
ChangesListFilterGroup
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
ChangesListFilter
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
ChangesFeed
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
ChangesList
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (30, 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 75)
* Component uses 316 operators

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

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

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

* Class has 482 logical lines of code
* Class has 800 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Probably bugged Too long Too dependent
EnhancedChangesList
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 94)
* Component uses 351 operators

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

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

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 79)
* Component uses 293 operators

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

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

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

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

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

* Class has 540 logical lines of code
* Class has 1468 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
WikitextContent
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
WikitextContentHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (12, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.
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 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 Probably bugged Too dependent
ContentModelChange
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.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
WikiTextStructure
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\Deferred\DeferredUpdatesScope
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\Deferred\SearchUpdate
Probably bugged warning
This component contains in theory 0.57 bugs.

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

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

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

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

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.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 222 logical lines of code
* Class has 439 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Probably bugged Too long Too dependent
MediaWiki\Deferred\LinksUpdate\CategoryLinksTable
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 long information
This class looks really long.

* Class has 201 logical lines of code
* Class has 282 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
MediaWiki\Deferred\LinksUpdate\LinksTable
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\Deferred\DeferredUpdatesScopeStack
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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\Deferred\CdnCacheUpdate
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.84 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\OutputTransform\Stages\HandleSectionLinks
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\OutputTransform\Stages\RenderDebugInfo
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
MediaWiki\OutputTransform\Stages\HandleTOCMarkers
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.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
UploadSourceAdapter
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
ImportableOldRevisionImporter
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.57 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 151)
* Component uses 373 operators

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

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

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

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

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

* Class has 753 logical lines of code
* Class has 1071 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
WikiRevision
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 279 logical lines of code
* Class has 611 lines of code

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

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

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

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

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

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Installer\WebInstallerLanguage
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
MediaWiki\Installer\SqliteInstaller
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

* Class has 220 logical lines of code
* Class has 298 lines of code

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

* object has lot of public methods (32, 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 142)
* Component uses 438 operators

Maybe you should delegate some 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 5.32 bugs.

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

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

* Class has 940 logical lines of code
* Class has 1577 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 34, so this class uses 34 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\Installer\WebInstaller
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should delegate some 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 3.5 bugs.

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

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

* Class has 561 logical lines of code
* Class has 975 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\Installer\WebInstallerName
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.84 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 50)
* Component uses 172 operators

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

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

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 252 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
MediaWiki\Installer\LocalSettingsGenerator
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.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
MediaWiki\Installer\Pingback
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\Installer\PostgresInstaller
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Probably bugged Too long
MediaWiki\Installer\MysqlUpdater
Probably bugged warning
This component contains in theory 1.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
MediaWiki\Installer\SqliteUpdater
Probably bugged warning
This component contains in theory 1.02 bugs.

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

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

* object has lot of public methods (30, 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 28)
* Component uses 103 operators

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

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

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

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

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

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

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

Maybe you should delegate some 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.63 bugs.

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

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

* Class has 293 logical lines of code
* Class has 387 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\Installer\DatabaseUpdater
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 95)
* Component uses 258 operators

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

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

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

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

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

* Class has 578 logical lines of code
* Class has 1124 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\Installer\PostgresSettingsForm
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\Installer\PostgresUpdater
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 60)
* Component uses 186 operators

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

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

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

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

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

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

* Class has 223 logical lines of code
* Class has 541 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\Config\EtcdConfig
Probably bugged warning
This component contains in theory 1 bugs.

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

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

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

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

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

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

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

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

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

Maybe you should check your unit tests for this class.
Blob / God object Too complex method code Probably bugged
Wikimedia\WRStats\MetricSpec
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
Wikimedia\WRStats\WRStatsRateLimiter
Probably bugged warning
This component contains in theory 0.37 bugs.

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

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

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

Maybe you should delegate some 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.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 512 logical lines of code
* Class has 724 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
FSFileBackend
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 158)
* Component uses 466 operators

Maybe you should delegate some 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 4.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 701 logical lines of code
* Class has 965 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
MemoryFileBackend
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 207 logical lines of code
* Class has 232 lines of code

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

* object has lot of public methods (63, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=32)
* 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 68)
* Component uses 213 operators

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 262)
* Component uses 771 operators

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

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

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

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
FileOpBatch
Too complex method code error
This class looks really complex.

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

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 203)
* Component uses 631 operators

Maybe you should delegate some 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 6.47 bugs.

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

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

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

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

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

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

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

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

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

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

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

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

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Probably bugged Too long
Wikimedia\Diff\DiffEngine
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 150)
* Component uses 633 operators

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

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

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

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

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

* Class has 459 logical lines of code
* Class has 657 lines of code

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

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

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

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

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

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

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

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

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

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
QuorumLockManager
Probably bugged warning
This component contains in theory 0.49 bugs.

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 99)
* Component uses 260 operators

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

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

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

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

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

* Class has 425 logical lines of code
* Class has 691 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
Wikimedia\Http\HttpAcceptParser
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
CryptHKDF
Probably bugged warning
This component contains in theory 0.35 bugs.

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

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

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

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

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

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

* Class has 377 logical lines of code
* Class has 872 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
Wikimedia\Rdbms\InsertQueryBuilder
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
Wikimedia\Rdbms\DoctrineAbstractSchemaTrait
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
Wikimedia\Rdbms\DatabaseFactory
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
Wikimedia\Rdbms\DBConnRef
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

* Class has 708 logical lines of code
* Class has 829 lines of code

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 95)
* Component uses 312 operators

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

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

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

* Class has 500 logical lines of code
* Class has 728 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
Wikimedia\Rdbms\Replication\ReplicationReporter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

* Class has 227 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
Wikimedia\Rdbms\DatabasePostgres
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (42, 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 98)
* Component uses 411 operators

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

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

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

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

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

* Class has 669 logical lines of code
* Class has 874 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
Wikimedia\Rdbms\TransactionManager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 99)
* Component uses 284 operators

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

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

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

* Class has 584 logical lines of code
* Class has 797 lines of code

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 300)
* Component uses 900 operators

Maybe you should delegate some 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 11.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 1932 logical lines of code
* Class has 2830 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 40, so this class uses 40 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
Wikimedia\Rdbms\DatabaseSqlite
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 88)
* Component uses 310 operators

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

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

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

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

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

* Class has 515 logical lines of code
* Class has 745 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
Wikimedia\Rdbms\DatabaseDomain
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
Wikimedia\Rdbms\MySQLPrimaryPos
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
Wikimedia\Rdbms\LoadMonitor
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.
Probably bugged
Wikimedia\Rdbms\TransactionProfiler
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 52)
* Component uses 115 operators

Maybe you should delegate some 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 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 262 logical lines of code
* Class has 447 lines of code

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

* object has lot of public methods (51, 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 272)
* Component uses 639 operators

Maybe you should delegate some 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 6.19 bugs.

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

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

* Class has 1209 logical lines of code
* Class has 1675 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
Wikimedia\Rdbms\ServerInfo
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
Wikimedia\Rdbms\Platform\SQLPlatform
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (72, 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 275)
* Component uses 760 operators

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

* Class has 1228 logical lines of code
* Class has 1601 lines of code

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

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

Maybe you should delegate some 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.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 281 logical lines of code
* Class has 555 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
Wikimedia\Rdbms\LBFactoryMulti
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 52)
* Component uses 95 operators

Maybe you should delegate some 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.73 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 92)
* Component uses 199 operators

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

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

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

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

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

* Class has 447 logical lines of code
* Class has 587 lines of code

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 59)
* Component uses 172 operators

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

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

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

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

Maybe you should check your unit tests for this class.
Too complex class code Too complex method code Probably bugged
Wikimedia\ParamValidator\TypeDef\NumericDef
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 52)
* Component uses 126 operators

Maybe you should delegate some 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.71 bugs.

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

Maybe you should check your unit tests for this class.
Too complex class code Too complex method code Probably bugged
Wikimedia\ParamValidator\TypeDef\StringDef
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.35 bugs.

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

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
Wikimedia\ParamValidator\TypeDef\EnumDef
Probably bugged warning
This component contains in theory 0.6 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
Wikimedia\ParamValidator\TypeDef\UploadDef
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
Wikimedia\ParamValidator\Util\UploadedFileStream
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

Maybe you should delegate some 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 2.27 bugs.

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

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

* Class has 370 logical lines of code
* Class has 662 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
Wikimedia\Mime\MimeMap
Probably bugged warning
This component contains in theory 2.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 212 logical lines of code
* Class has 223 lines of code

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

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

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

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

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

* Class has 248 logical lines of code
* Class has 445 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
MSCompoundFileReader
Probably bugged warning
This component contains in theory 1.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 214 logical lines of code
* Class has 289 lines of code

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

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

Maybe you should delegate some 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 3.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 620 logical lines of code
* Class has 977 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
RiffExtractor
Too complex method code error
This class looks really complex.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 69)
* Component uses 236 operators

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

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

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

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

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

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

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

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

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

Maybe you should delegate some 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.71 bugs.

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

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

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

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
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.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
AssembleUploadChunksJob
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.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
DoubleRedirectJob
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.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
HTMLCacheUpdateJob
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
UploadJobTrait
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
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.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
RecentChangesUpdateJob
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
RefreshLinksJob
Too complex class code error
This class looks really complex.

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

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

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

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

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

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

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

* Class has 488 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 Probably bugged Too long
JobQueueGroup
Too complex class code error
This class looks really complex.

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

Maybe you should delegate some 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.91 bugs.

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

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

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

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

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

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

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

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

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

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

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

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

* Class has 291 logical lines of code
* Class has 736 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
BanConverter
Too long information
This class looks really long.

* Class has 879 logical lines of code
* Class has 1017 lines of code

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

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

Maybe you should check your unit tests for this class.
Probably bugged
CrhConverter
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 272 logical lines of code
* Class has 330 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
UzConverter
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
IuConverter
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.
Probably bugged
KuConverter
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
SrConverter
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
ShiConverter
Probably bugged warning
This component contains in theory 0.56 bugs.

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 142)
* Component uses 491 operators

Maybe you should delegate some 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 4.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 769 logical lines of code
* Class has 1359 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
LanguageConverter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 141)
* Component uses 502 operators

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

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

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

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

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

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

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

Maybe you should delegate some 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 3.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 679 logical lines of code
* Class has 1136 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
ConverterRule
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 86)
* Component uses 215 operators

Maybe you should delegate some 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.47 bugs.

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 526)
* Component uses 1850 operators

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

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

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

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
LanguageCode
Probably bugged warning
This component contains in theory 0.86 bugs.

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

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

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.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 212 logical lines of code
* Class has 366 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
ProtectLogFormatter
Probably bugged warning
This component contains in theory 0.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
BlockLogFormatter
Too complex class code error
This class looks really complex.

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 74)
* Component uses 250 operators

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

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

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

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
LogFormatter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

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

* Class has 569 logical lines of code
* Class has 885 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
ManualLogEntry
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.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 229 logical lines of code
* Class has 448 lines of code

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 53)
* Component uses 131 operators

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

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

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

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

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

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

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

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

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

* Class has 301 logical lines of code
* Class has 444 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\MainConfigNames
Probably bugged warning
This component contains in theory 2.35 bugs.

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

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

* Class has 743 logical lines of code
* Class has 3715 lines of code

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

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

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

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

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

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

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

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

Maybe you should delegate some code to other objects or split complex method.
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 375 logical lines of code
* Class has 534 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 class code error
This class looks really complex.

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

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 class code Too complex method code Probably bugged
BitmapMetadataHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 516)
* Component uses 665 operators

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

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 7.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 1316 logical lines of code
* Class has 1741 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 76)
* Component uses 182 operators

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

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

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

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

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

* Class has 242 logical lines of code
* Class has 332 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
PNGHandler
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
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.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 372 logical lines of code
* Class has 563 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 36)

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

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

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

* Class has 206 logical lines of code
* Class has 297 lines of code

Maybe your class should not exceed 200 lines of logical 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.71 bugs.

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

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

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

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

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

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 271 logical lines of code
* Class has 340 lines of code

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 64)
* Component uses 192 operators

Maybe you should delegate some 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 1.61 bugs.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

* Class has 358 logical lines of code
* Class has 515 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
ExifBitmapHandler
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
MediaHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 53)
* Component uses 224 operators

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

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

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

* Class has 303 logical lines of code
* Class has 363 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
FileBackendGroup
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.
Probably bugged
MediaWiki\Title\Title
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 305)
* Component uses 1076 operators

Maybe you should delegate some 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 9.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 1701 logical lines of code
* Class has 3372 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 36, so this class uses 36 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\Title\TitleFactory
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
MediaWiki\Title\TitleValue
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

* object has lot of public methods (32, 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 42)
* Component uses 133 operators

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

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

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

* Class has 244 logical lines of code
* Class has 527 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Probably bugged Too long
MediaWiki\Languages\Data\NormalizeAr
Probably bugged warning
This component contains in theory 4.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.
Probably bugged
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 1189 lines of code

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

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

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

* Class has 635 logical lines of code
* Class has 1093 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
MediaWiki\Languages\Data\ZhConversion
Probably bugged warning
This component contains in theory 193.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
LanguageTyv
Too complex class code error
This class looks really complex.

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

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

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

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

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

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

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

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 227 logical lines of code
* Class has 271 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
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
MediaWiki\EditPage\Constraint\EditConstraintFactory
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 dependent
MediaWiki\EditPage\TextConflictHelper
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.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.
Blob / God object Probably bugged
MediaWiki\EditPage\IntroMessageBuilder
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 77)
* Component uses 154 operators

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

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

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

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

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

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\EditPage\PreloadedContentBuilder
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.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
MediaWiki\EditPage\TemplatesOnThisPageFormatter
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\EditPage\EditPage
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

Maybe you should delegate some 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 4.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 763 logical lines of code
* Class has 1261 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\ResourceLoader\Context
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

* Class has 262 logical lines of code
* Class has 446 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\ResourceLoader\Module
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

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

* Class has 397 logical lines of code
* Class has 1031 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
Wikimedia\DependencyStore\SqlModuleDependencyStore
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\ResourceLoader\MessageBlobStore
Probably bugged warning
This component contains in theory 0.37 bugs.

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 223)
* Component uses 613 operators

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 65)
* Component uses 202 operators

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

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

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

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
MediaWiki\ResourceLoader\StartUpModule
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.89 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 52)
* Component uses 144 operators

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

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

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 250 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
MediaWiki\ResourceLoader\Image
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 42)
* Component uses 133 operators

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 75)
* Component uses 163 operators

Maybe you should delegate some 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.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 295 logical lines of code
* Class has 415 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\ResourceLoader\VueComponentParser
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\ResourceLoader\ImageModule
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

Maybe you should delegate some 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 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 217 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
MediaWiki\RenameUser\RenameuserSQL
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.98 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 87)
* Component uses 217 operators

Maybe you should delegate some code to other objects.
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 386 logical lines of code
* Class has 702 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 Probably bugged Too long Too dependent
MediaWiki\Block\AbstractBlock
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.43 bugs.

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

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

* Class has 203 logical lines of code
* Class has 478 lines of code

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

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

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

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

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

* Class has 292 logical lines of code
* Class has 595 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\BlockRestrictionStore
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.
Probably bugged
MediaWiki\Block\CompositeBlock
Probably bugged warning
This component contains in theory 0.37 bugs.

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

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

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

Maybe you should delegate some 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 6.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 956 logical lines of code
* Class has 1418 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\BlockUser
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 79)
* Component uses 200 operators

Maybe you should delegate some 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.51 bugs.

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

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

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

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

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

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\ExternalLinks\LinkFilter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

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

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

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.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
MediaWiki\User\UserTimeCorrection
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.4 bugs.

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

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

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

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

Maybe you should delegate some 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 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 class code Too complex method code Probably bugged
MediaWiki\User\UserNameUtils
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.58 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 114)
* Component uses 288 operators

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

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

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

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

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

* Class has 538 logical lines of code
* Class has 925 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 class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\User\UserFactory
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.57 bugs.

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

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

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

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

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

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

* Class has 315 logical lines of code
* Class has 582 lines of code

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

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

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

* Class has 252 logical lines of code
* Class has 422 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\User\UserGroupMembership
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
MediaWiki\User\User
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should delegate some 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 7.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 1545 logical lines of code
* Class has 2923 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 44, so this class uses 44 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\User\Options\UserOptionsManager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 77)
* 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 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 316 logical lines of code
* Class has 570 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
MediaWiki\User\ActorMigrationBase
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.85 bugs.

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

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

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
MediaWiki\User\TempUser\TempUserCreator
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
MediaWiki\User\TempUser\RealTempUserConfig
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\User\TalkPageNotificationManager
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
MediaWiki\Permissions\RestrictionStore
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 330 logical lines of code
* Class has 545 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
MediaWiki\Permissions\GroupPermissionsLookup
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
MediaWiki\Permissions\UserAuthority
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.56 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 257)
* Component uses 526 operators

Maybe you should delegate some 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 5.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 735 logical lines of code
* Class has 1369 lines of code

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 51)
* Component uses 112 operators

Maybe you should delegate some 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 0.81 bugs.

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

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

* object has lot of public methods (13, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.
Blob / God object
MediaWiki\Auth\Throttler
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
MediaWiki\Auth\ConfirmLinkSecondaryAuthenticationProvider
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
MediaWiki\Auth\TemporaryPasswordPrimaryAuthenticationProvider
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 292)
* Component uses 751 operators

Maybe you should delegate some 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 8.91 bugs.

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

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

* Class has 1380 logical lines of code
* Class has 2019 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 46, so this class uses 46 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\Auth\AbstractPreAuthenticationProvider
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

Maybe you should delegate some 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.77 bugs.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 48)
* Component uses 107 operators

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 116)
* Component uses 284 operators

Maybe you should delegate some 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.87 bugs.

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

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

* Class has 416 logical lines of code
* Class has 532 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
WatchedItemStore
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 139)
* Component uses 411 operators

Maybe you should delegate some 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 4.68 bugs.

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

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

* Class has 802 logical lines of code
* Class has 1296 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 33, so this class uses 33 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
ExtensionJsonValidator
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.
Too complex method code
VersionChecker
Too complex method code error
This class looks really complex.

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

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

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

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

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

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

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

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

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

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
ExtensionProcessor
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 154)
* Component uses 266 operators

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

* Class has 205 logical lines of code
* Class has 341 lines of code

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

* object has lot of public methods (130, 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 325)
* Component uses 1108 operators

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

* Class has 2161 logical lines of code
* Class has 4164 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 50, so this class uses 50 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
PHPVersionCheck
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
MediaWiki\MediaWikiServices
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

* Class has 976 logical lines of code
* Class has 1875 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 203, so this class uses 203 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Probably bugged Too long Too dependent
MediaWiki\CommentFormatter\CommentParser
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 247 logical lines of code
* Class has 417 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\CommentFormatter\CommentFormatter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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.
Blob / God object Too complex method code Probably bugged
PPNode_Hash_Tree
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 146)
* Component uses 462 operators

Maybe you should delegate some 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 5.61 bugs.

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

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

* Class has 950 logical lines of code
* Class has 1562 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\Parser\MagicWordArray
Too complex class code error
This class looks really complex.

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

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

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

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

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* Component uses 158 operators

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

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

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 288 logical lines of code
* Class has 387 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
ParserFactory
Too dependent information
This class looks use really high number of components.

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

Maybe you should check why this class has lot of dependencies.
Too dependent
BlockLevelPass
Too complex class code error
This class looks really complex.

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

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

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

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

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

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

* Class has 393 logical lines of code
* Class has 555 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\Parser\Parsoid\LanguageVariantConverter
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
MediaWiki\Parser\Parsoid\ParsoidOutputAccess
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
MediaWiki\Parser\Parsoid\HtmlToContentTransform
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* Component uses 150 operators

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

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

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

* Class has 332 logical lines of code
* Class has 508 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Too complex class code Probably bugged Too long Too dependent
MediaWiki\Parser\Parsoid\ParsoidParser
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\Parser\Parsoid\Config\SiteConfig
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

* Algorithms are complex (Total cyclomatic complexity of class is 58)
* Component uses 226 operators

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

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

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

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

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

* Class has 469 logical lines of code
* Class has 619 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\Parser\Parsoid\Config\DataAccess
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.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 233 logical lines of code
* Class has 338 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
MediaWiki\Parser\Parsoid\Config\PageConfigFactory
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
ParserCache
Too complex class code error
This class looks really complex.

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

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

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

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 284 logical lines of code
* Class has 510 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
DateFormatter
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.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 complex method code Probably bugged
ParserOptions
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

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

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

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.35 bugs.

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

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

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

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

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

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

* object has lot of public methods (90, 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 657)
* Component uses 2300 operators

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

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

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

* object has lot of public methods (88, 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 221)
* Component uses 615 operators

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

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

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

* Class has 1327 logical lines of code
* Class has 2687 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
CoreMagicVariables
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 83)
* Component uses 78 operators

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

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

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

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

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

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

* object has lot of public methods (78, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=83)
* 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 191)
* Component uses 613 operators

Maybe you should delegate some 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 5.87 bugs.

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

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

* Class has 1034 logical lines of code
* Class has 1450 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
Preprocessor_Hash
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 121)
* Component uses 454 operators

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

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

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

* Class has 503 logical lines of code
* Class has 673 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
ProfilerExcimer
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
Profiler
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
SectionProfiler
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
ProfilerXhprof
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.62 bugs.

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

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

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

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

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

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 367 logical lines of code
* Class has 686 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
MediaWiki\Settings\SettingsBuilder
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

Maybe you should delegate some 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.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 337 logical lines of code
* Class has 738 lines of code

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

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\Settings\Source\EtcdSource
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
MediaWiki\Settings\Source\ReflectionSchemaSource
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
MediaWiki\Settings\Source\JsonSchemaTrait
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
MediaWiki\Settings\Config\ConfigSchemaAggregator
Too complex class code error
This class looks really complex.

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

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

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

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

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

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

* Class has 224 logical lines of code
* Class has 433 lines of code

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

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

Maybe you should delegate some code to other objects or split complex method.
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
MWRestrictions
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* Component uses 257 operators

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

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

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

* Class has 315 logical lines of code
* Class has 532 lines of code

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

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=9)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
MediaWiki\Utils\UrlUtils
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 79)
* Component uses 203 operators

Maybe you should delegate some 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.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 264 logical lines of code
* Class has 456 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\Utils\GitInfo
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (13, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=6)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 54)
* 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 11)

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 232 logical lines of code
* Class has 358 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
AutoloadGenerator
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.
Probably bugged
ExternalStoreDB
Probably bugged warning
This component contains in theory 1.04 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
ExternalStoreAccess
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
MediaWiki\HTMLForm\CodexHTMLForm
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.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
MediaWiki\HTMLForm\HTMLForm
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (63, 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 153)
* 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 22)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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 933 logical lines of code
* Class has 1934 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\HTMLForm\HTMLFormField
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (38, 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 182)
* Component uses 453 operators

Maybe you should delegate some 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.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 713 logical lines of code
* Class has 1235 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\HTMLForm\Field\HTMLTextAreaField
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
MediaWiki\HTMLForm\Field\HTMLCheckField
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
MediaWiki\HTMLForm\Field\HTMLDateTimeField
Probably bugged warning
This component contains in theory 0.56 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\HTMLForm\Field\HTMLFormFieldCloner
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 80)
* Component uses 220 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 15)

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 343 logical lines of code
* Class has 477 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\HTMLForm\Field\HTMLMultiSelectField
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.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 Too complex method code Probably bugged
MediaWiki\HTMLForm\Field\HTMLUsersMultiselectField
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\HTMLForm\Field\HTMLTitleTextField
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
MediaWiki\HTMLForm\Field\HTMLTextField
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
MediaWiki\HTMLForm\Field\HTMLAutoCompleteSelectField
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.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
MediaWiki\HTMLForm\Field\HTMLSelectAndOtherField
Probably bugged warning
This component contains in theory 0.77 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\HTMLForm\Field\HTMLSelectOrOtherField
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
MediaWiki\HTMLForm\Field\HTMLTimezoneField
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
MediaWiki\HTMLForm\Field\HTMLTagMultiselectField
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
MediaWiki\HTMLForm\Field\HTMLButtonField
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
MediaWiki\HTMLForm\Field\HTMLUserTextField
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 17)

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
MediaWiki\HTMLForm\Field\HTMLRadioField
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
MediaWiki\HTMLForm\Field\HTMLTitlesMultiselectField
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.36 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\HTMLForm\Field\HTMLCheckMatrix
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.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.
Blob / God object Probably bugged
MediaWiki\HTMLForm\OOUIHTMLForm
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.76 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Revision\MainSlotRoleHandler
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.
Too complex method code
MediaWiki\Revision\RenderedRevision
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.59 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Revision\RevisionStore
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 264)
* Component uses 767 operators

Maybe you should delegate some 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 9.87 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 1188 logical lines of code
* Class has 2279 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 54, so this class uses 54 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\Revision\RevisionArchiveRecord
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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
MediaWiki\Revision\RevisionRecord
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (24, 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.5 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 216 logical lines of code
* Class has 549 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
MediaWiki\Revision\MutableRevisionRecord
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (13, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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\Revision\SlotRecord
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility 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 107 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 0.84 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 252 logical lines of code
* Class has 568 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 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
MediaWiki\Revision\RevisionStoreRecord
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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
MediaWiki\Shell\Command
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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
MWHttpRequest
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (18, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=6)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 70)
* Component uses 198 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 375 logical lines of code
* Class has 645 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\Http\HttpRequestFactory
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.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
GuzzleHttpRequest
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.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
MediaWiki\Http\MwHttpRequestToResponseInterfaceAdapter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (15, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
MediaWiki\Watchlist\WatchlistManager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 118 operators

Maybe you should delegate some 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.73 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 208 logical lines of code
* Class has 395 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\Preferences\DefaultPreferencesFactory
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 202)
* Component uses 598 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 54)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 8.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 840 logical lines of code
* Class has 1176 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 48, so this class uses 48 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\Preferences\SignatureValidator
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.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 complex method code Probably bugged
FormatJson
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 19)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.57 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Json\JsonCodec
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 51)
* Component uses 97 operators

Maybe you should delegate some 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.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 class code Too complex method code Probably bugged
MWLBFactory
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 115 operators

Maybe you should delegate some 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.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 complex class code Too complex method code Probably bugged
SkinTemplate
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 191)
* Component uses 515 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 79)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 6.58 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 773 logical lines of code
* Class has 1254 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 responsibility principle.

* object has lot of public methods (46, 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 224)
* Component uses 770 operators

Maybe you should delegate some 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 8.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 1142 logical lines of code
* Class has 1980 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 27, so this class uses 27 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\Skin\SkinComponentFooter
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 45)
* Component uses 116 operators

Maybe you should delegate some 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.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 complex class code Too complex method code Probably bugged
MediaWiki\Skin\SkinComponentLink
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.62 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Skin\SkinComponentMenu
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.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
MediaWiki\Skin\SkinComponentSearch
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
MediaWiki\Skin\SkinComponentListItem
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.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
BaseTemplate
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 46)
* Component uses 96 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 25)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.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 class code Too complex method code Probably bugged
UploadStash
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.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 226 logical lines of code
* Class has 418 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
UploadBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (49, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=36)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 279)
* Component uses 822 operators

Maybe you should delegate some 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 7.74 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 1148 logical lines of code
* Class has 1863 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 28, so this class uses 28 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
UploadFromUrl
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (13, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=10)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 37)
* Component uses 133 operators

Maybe you should delegate some 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.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 218 logical lines of code
* Class has 348 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
UploadFromChunks
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 223 logical lines of code
* Class has 376 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
AutoLoader
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.76 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Pager\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.59 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Pager\IndexPager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 61)
* Component uses 210 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 13)

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 395 logical lines of code
* Class has 854 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\Pager\TablePager
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (13, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.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 221 logical lines of code
* Class has 425 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
SlotDiffRenderer
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
MediaWiki\Diff\TextDiffer\ManifoldTextDiffer
Probably bugged warning
This component contains in theory 0.57 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\Diff\TextDiffer\Wikidiff2TextDiffer
Probably bugged warning
This component contains in theory 0.57 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
DifferenceEngine
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (41, 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 250)
* Component uses 746 operators

Maybe you should delegate some 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.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 1114 logical lines of code
* Class has 1827 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
TextSlotDiffRenderer
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.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.
Blob / God object Probably bugged
MediaWiki\Maintenance\ForkController
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 14)

Maybe you should delegate some code to other objects or split complex method.
Too complex method code
MediaWiki\Maintenance\OrderedStreamingForkController
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\Sparql\SparqlClient
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
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.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
IRCColourfulRCFeedFormatter
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.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
MediaWiki\Rest\ConditionalHeaderUtil
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 25)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.38 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Rest\RequestData
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\Rest\Handler
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (18, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=5)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 38)
* Component uses 121 operators

Maybe you should delegate some code to other objects.
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 285 logical lines of code
* Class has 772 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\Rest\Router
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 47)
* Component uses 154 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 14)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 298 logical lines of code
* Class has 510 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
MediaWiki\Rest\HeaderParser\HttpDate
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.
Probably bugged
MediaWiki\Rest\Handler\Helper\PageRestHelperFactory
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.
Too dependent
MediaWiki\Rest\Handler\Helper\PageContentHelper
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility 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.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 32)
* Component uses 96 operators

Maybe you should delegate some code to other 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 Too complex class code Probably bugged
MediaWiki\Rest\Handler\Helper\HtmlInputTransformHelper
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 78)
* 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 27)

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 280 logical lines of code
* Class has 479 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\Rest\Handler\Helper\HtmlOutputRendererHelper
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (19, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 58)
* Component uses 148 operators

Maybe you should delegate some code to other objects.
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 long information
This class looks really long.

* Class has 331 logical lines of code
* Class has 592 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 37, so this class uses 37 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Probably bugged Too long Too dependent
MediaWiki\Rest\Handler\Helper\RevisionContentHelper
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
MediaWiki\Rest\Handler\SearchHandler
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 109 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 0.91 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex class code Probably bugged
MediaWiki\Rest\Handler\PageHistoryCountHandler
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 58)
* Component uses 167 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 20)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 287 logical lines of code
* Class has 415 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\Rest\Handler\UpdateHandler
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.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
MediaWiki\Rest\Handler\TransformHandler
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.
Too complex method code
MediaWiki\Rest\Handler\PageHistoryHandler
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 61)
* 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 27)

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 long information
This class looks really long.

* Class has 243 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
MediaWiki\Rest\Handler\ParsoidHandler
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 131)
* Component uses 342 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 30)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.32 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 509 logical lines of code
* Class has 798 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 40, so this class uses 40 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\Rest\Handler\CompareHandler
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
MediaWiki\Rest\EntryPoint
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\Rest\Validator\Validator
Probably bugged warning
This component contains in theory 0.75 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\Rest\PathTemplateMatcher\PathMatcher
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\Rest\ResponseFactory
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (16, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.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.
Blob / God object Probably bugged
ApiUserrights
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.6 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiQueryAllUsers
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* Component uses 136 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 48)

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 208 logical lines of code
* Class has 251 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
ApiQueryLogEvents
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 82)
* 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 43)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 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 120)
* Component uses 268 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 110)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.62 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 435 logical lines of code
* Class has 548 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
ApiQueryAllDeletedRevisions
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 76)
* 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 75)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.05 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 282 logical lines of code
* Class has 332 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
ApiQueryRevisionsBase
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 138)
* Component uses 344 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 39)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.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 long information
This class looks really long.

* Class has 495 logical lines of code
* Class has 621 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 22, so this class uses 22 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
ApiFeedRecentChanges
Probably bugged warning
This component contains in theory 0.37 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
ApiQueryQueryPage
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.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
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.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
MediaWiki\Api\ApiEntryPoint
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
ApiQueryInfo
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 131)
* Component uses 355 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 57)

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 646 logical lines of code
* Class has 794 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 22, so this class uses 22 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
ApiFormatXml
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 59)
* 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 45)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.92 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex class code Too complex method code Probably bugged
ApiQueryAllCategories
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 17)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.58 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiQueryAllLinks
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 47)
* 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 42)

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 235 logical lines of code
* Class has 255 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
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.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
ApiHelp
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=10)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 82)
* Component uses 269 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 55)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.14 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 398 logical lines of code
* Class has 483 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
ApiResult
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (33, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=21)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 173)
* 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 74)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.08 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 598 logical lines of code
* Class has 1092 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
ApiOpenSearch
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 12)

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 226 logical lines of code
* Class has 290 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex method code Probably bugged Too long
ApiQuerySiteinfo
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (15, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 149)
* Component uses 441 operators

Maybe you should delegate some 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 5.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 804 logical lines of code
* Class has 866 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 34, so this class uses 34 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
ApiQueryRandom
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 15)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.69 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiQueryFilearchive
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 62)
* Component uses 149 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 62)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.37 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex class code 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.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
ApiWatch
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.56 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
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.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
ApiQueryAllPages
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 45)
* Component uses 102 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 43)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.14 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex class code Too complex method code Probably bugged
ApiQueryWatchlist
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 100)
* 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 38)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.05 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 322 logical lines of code
* Class has 363 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
ApiQueryIWLinks
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.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
ApiQueryProtectedTitles
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
ApiContinuationManager
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
ApiPurge
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.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
ApiBlock
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.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 complex method code Probably bugged
ApiQueryUsers
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* Component uses 109 operators

Maybe you should delegate some 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 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 long information
This class looks really long.

* Class has 227 logical lines of code
* Class has 253 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
ApiQuerySearch
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 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 33)

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 273 logical lines of code
* Class has 346 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
ApiExpandTemplates
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 0.71 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiPageSet
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (28, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 163)
* Component uses 416 operators

Maybe you should delegate some 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.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 873 logical lines of code
* Class has 1422 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
ApiQuery
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 54)
* Component uses 146 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 24)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 326 logical lines of code
* Class has 456 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
ApiMessageTrait
Probably bugged warning
This component contains in theory 0.48 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Probably bugged
MediaWiki\Api\ApiHookRunner
Probably bugged warning
This component contains in theory 0.76 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 44, so this class uses 44 different external components.

Maybe you should check why this class has lot of dependencies.
Probably bugged Too dependent
ApiQueryAllRevisions
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.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
ApiProtect
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.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
ApiQueryBlocks
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 69)
* Component uses 192 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 58)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.39 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 298 logical lines of code
* Class has 331 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
ApiCSPReport
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
ApiQueryUserInfo
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 45)
* Component uses 128 operators

Maybe you should delegate some 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.18 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has 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 276 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
ApiFormatBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (12, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=3)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 13)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 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.
Blob / God object Too complex method code Probably bugged
ApiQueryRecentChanges
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 139)
* Component uses 289 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 88)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.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 421 logical lines of code
* Class has 502 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
ApiQueryImageInfo
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=9)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 139)
* Component uses 320 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 76)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.07 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 449 logical lines of code
* Class has 597 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Too complex class code Too complex method code Probably bugged Too long
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.9 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiRollback
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
ApiClientLogin
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=8)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
ApiQueryDuplicateFiles
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.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
ApiRevisionDelete
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.58 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
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
ApiAuthManagerHelper
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=4)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 41)
* Component uses 110 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 13)

Maybe you should delegate some code to other objects or split complex method.
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.
Blob / God object Too complex class code Too complex method code Probably bugged
ApiQueryBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 43)
* Component uses 110 operators

Maybe you should delegate some code to other objects.
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 long information
This class looks really long.

* Class has 258 logical lines of code
* Class has 550 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
ApiQueryUserContribs
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 112)
* Component uses 299 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 46)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.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 424 logical lines of code
* Class has 481 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
ApiQueryLanguageinfo
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.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
ApiQueryExtLinksUsage
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.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
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.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiQueryAllImages
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 45)
* Component uses 99 operators

Maybe you should delegate some 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.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 complex class code 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 158)
* Component uses 431 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 112)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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 686 logical lines of code
* Class has 822 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 34, so this class uses 34 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
ApiQueryBacklinksprop
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 54)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 263 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
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.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
ApiMove
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 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.
Blob / God object Too complex method code Probably bugged
ApiQueryDeletedrevs
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 82)
* Component uses 209 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 80)

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 300 logical lines of code
* Class has 338 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
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.3 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 213 logical lines of code
* Class has 261 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
ApiOptions
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
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.09 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (56, 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 180)
* Component uses 452 operators

Maybe you should delegate some 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 4.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 921 logical lines of code
* Class has 1850 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 27, so this class uses 27 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
ApiQueryAllMessages
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 37)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.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
ApiQueryExternalLinks
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.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
ApiComparePages
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 125)
* Component uses 278 operators

Maybe you should delegate some 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.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 487 logical lines of code
* Class has 590 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
ApiLogin
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 23)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.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.
Blob / God object Too complex method code Probably bugged
ApiStashEdit
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 18)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.59 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Blob / God object Too complex method code Probably bugged
ApiUnblock
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 14)

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
ApiQueryLangLinks
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.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
ApiQueryDeletedRevisions
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 48)
* Component uses 109 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 47)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 complex class code Too complex method code Probably bugged
ApiImport
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 14)

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.
Blob / God object Too complex method code Probably bugged
ApiMain
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (19, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=6)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 211)
* Component uses 592 operators

Maybe you should delegate some 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 7.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 1090 logical lines of code
* Class has 1620 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
ApiQueryLinks
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 26)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.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
ApiDelete
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.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
ApiSetNotificationTimestamp
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.74 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiQueryBacklinks
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 81)
* Component uses 245 operators

Maybe you should delegate some 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.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 369 logical lines of code
* Class has 449 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 50)
* Component uses 123 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 37)

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 225 logical lines of code
* Class has 326 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
ApiQueryRevisions
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 70)
* Component uses 187 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 70)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.07 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 249 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
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.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
ApiUpload
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (11, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=9)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 161)
* Component uses 340 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 28)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 4.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 587 logical lines of code
* Class has 821 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 27, so this class uses 27 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
ApiErrorFormatter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (12, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.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.
Blob / God object Probably bugged
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
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.58 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
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
ApiParamInfo
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 68)
* Component uses 167 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 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 306 logical lines of code
* Class has 341 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
ApiQueryIWBacklinks
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.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
ApiUndelete
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 17)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.38 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
ApiFeedContributions
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.76 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex method code Probably bugged Too dependent
MediaWiki\MainConfigSchema
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (27, 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.
Probably bugged warning
This component contains in theory 12.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 1123 logical lines of code
* Class has 9036 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
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.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 223 logical lines of code
* Class has 325 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
TraditionalImageGallery
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 53)
* Component uses 164 operators

Maybe you should delegate some 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 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 206 logical lines of code
* Class has 363 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
ImageGalleryBase
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (13, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=5)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.44 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Blob / God object Probably bugged
MediaWiki\Session\SessionBackend
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 88)
* Component uses 207 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 31)

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 410 logical lines of code
* Class has 662 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\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\BotPasswordSessionProvider
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=3)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
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.
Blob / God object Probably bugged
MediaWiki\Session\SessionProvider
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (28, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=19)
* 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.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 203 logical lines of code
* Class has 688 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 21, so this class uses 21 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Probably bugged Too long Too dependent
MediaWiki\Session\SessionManager
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (22, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 161)
* Component uses 382 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 53)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.18 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 604 logical lines of code
* Class has 879 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\PHPSessionHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.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.
Blob / God object Too complex method code Probably bugged
MediaWiki\Session\CookieSessionProvider
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (10, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 123 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 1.01 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 223 logical lines of code
* Class has 318 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\Session\Session
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 35)
* Component uses 145 operators

Maybe you should delegate some code to other objects.
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 long information
This class looks really long.

* Class has 362 logical lines of code
* Class has 635 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
MediaWiki\CommentStore\CommentStore
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.91 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Html\FormOptions
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 36)
* Component uses 83 operators

Maybe you should delegate some 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.57 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 200 logical lines of code
* Class has 376 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\Html\TemplateParser
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.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
MediaWiki\Html\Html
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 102)
* Component uses 284 operators

Maybe you should delegate some 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 3.1 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 479 logical lines of code
* Class has 1013 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
WikiExporter
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 54)
* Component uses 209 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 22)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.73 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 324 logical lines of code
* Class has 483 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
BaseDump
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
XmlDumpWriter
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (11, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 59)
* Component uses 342 operators

Maybe you should delegate some 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.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 360 logical lines of code
* Class has 563 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\LinkedData\PageDataRequestHandler
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\Linker\Linker
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (53, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=55)
* 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 321)
* Component uses 982 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 68)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 9.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 1158 logical lines of code
* Class has 1979 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\Linker\LinkRenderer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 37)
* Component uses 128 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 0.95 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 240 logical lines of code
* Class has 484 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
MediaWiki\Linker\DummyLinker
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (48, 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.
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 245 logical lines of code
* Class has 392 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
MediaWiki\Linker\LinkTargetStore
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
IcuCollation
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 15)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 439 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
Xml
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (35, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=36)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* 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 11)

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 370 logical lines of code
* Class has 769 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\MediaWikiEntryPoint
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 86)
* Component uses 260 operators

Maybe you should delegate some 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.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 567 logical lines of code
* Class has 1028 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 33, so this class uses 33 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
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.07 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 223 logical lines of code
* Class has 349 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex method code Probably bugged Too long
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.5 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 366 logical lines of code
* Class has 513 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\Search\TitleMatcher
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.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
MediaWiki\Search\SearchWidgets\InterwikiSearchResultSetWidget
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
MediaWiki\Search\SearchWidgets\FullSearchResultWidget
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* Component uses 161 operators

Maybe you should delegate some code to other objects.
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 long information
This class looks really long.

* Class has 231 logical lines of code
* Class has 358 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Probably bugged Too long
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
MediaWiki\Search\SearchWidgets\SearchFormWidget
Probably bugged warning
This component contains in theory 1.18 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* 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.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
SearchEngine
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (30, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=18)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 52)
* 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 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 414 logical lines of code
* Class has 828 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
SearchSuggestionSet
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (15, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=5)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.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.
Blob / God object Probably bugged
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
PrefixSearch
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.77 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
Action
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (22, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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\Pager\HistoryPager
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* 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 26)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.04 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 312 logical lines of code
* Class has 446 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
WatchAction
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=10)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.49 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Blob / God object Too complex method code Probably bugged
MediaWiki\Actions\ActionEntryPoint
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 115)
* Component uses 270 operators

Maybe you should delegate some 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 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 397 logical lines of code
* Class has 595 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\Actions\ActionFactory
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.62 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
CreditsAction
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.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
DeleteAction
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 43)
* 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 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 327 logical lines of code
* Class has 405 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
McrUndoAction
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 50)
* 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 18)

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 271 logical lines of code
* Class has 335 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
HistoryAction
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.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
InfoAction
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 93)
* Component uses 323 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 63)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 3.8 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 427 logical lines of code
* Class has 573 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 32, so this class uses 32 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
RevertAction
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
RollbackAction
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 20)

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.
Blob / God object Too complex method code Probably bugged
MediaWiki\Actions\FileDeleteAction
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.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
RawAction
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 49)
* Component uses 134 operators

Maybe you should delegate some 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 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.
Blob / God object Too complex class code Too complex method code Probably bugged
MediaWiki\WikiMap\WikiMap
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
MediaWiki\SiteStats\SiteStatsInit
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 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.
Blob / God object Too complex method code Probably bugged
MediaWiki\SiteStats\SiteStats
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (11, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=16)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
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.
Blob / God object Probably bugged
MediaWiki\Storage\PageEditStash
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 36)
* 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 15)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.3 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 258 logical lines of code
* Class has 416 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\Storage\PageUpdater
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 85)
* Component uses 310 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 17)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 672 logical lines of code
* Class has 1353 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 39, so this class uses 39 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
MediaWiki\Storage\RevisionSlotsUpdate
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (14, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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\NameTableStore
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 long information
This class looks really long.

* Class has 203 logical lines of code
* Class has 383 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
MediaWiki\Storage\RevertedTagUpdate
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
MediaWiki\Storage\SqlBlobStore
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (12, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=6)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 63)
* Component uses 204 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 18)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 342 logical lines of code
* Class has 639 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\PageUpdaterFactory
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 28, so this class uses 28 different external components.

Maybe you should check why this class has lot of dependencies.
Too dependent
MediaWiki\Storage\DerivedPageDataUpdater
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 155)
* Component uses 397 operators

Maybe you should delegate some 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 3.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 752 logical lines of code
* Class has 1420 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 50, so this class uses 50 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\Interwiki\ClassicInterwikiLookup
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 44)
* Component uses 132 operators

Maybe you should delegate some 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.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 class code Too complex method code Probably bugged
MediaWiki\Page\PageCommandFactory
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 dependent information
This class looks use really high number of components.

* Efferent coupling is 47, so this class uses 47 different external components.

Maybe you should check why this class has lot of dependencies.
Probably bugged Too dependent
MediaWiki\Page\DeletePage
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 61)
* Component uses 212 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 16)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.07 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 409 logical lines of code
* Class has 697 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 36, so this class uses 36 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\Page\PageProps
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
MediaWiki\Page\ParserOutputAccess
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 17)

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 long information
This class looks really long.

* Class has 218 logical lines of code
* Class has 368 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
MediaWiki\Page\ProtectionForm
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 54)
* Component uses 172 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 14)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 long information
This class looks really long.

* Class has 295 logical lines of code
* Class has 415 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\Page\RollbackPage
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 43)
* Component uses 115 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 18)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.06 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 207 logical lines of code
* Class has 343 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 25, so this class uses 25 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
ImagePage
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 118)
* Component uses 393 operators

Maybe you should delegate some 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 4.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 598 logical lines of code
* Class has 830 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
WikiFilePage
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
MediaWiki\Page\MergeHistory
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 247 logical lines of code
* Class has 436 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 24, so this class uses 24 different external components.

Maybe you should check why this class has lot of dependencies.
Probably bugged Too long Too dependent
MediaWiki\Page\File\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.
Too complex method code
PageArchive
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\Page\UndeletePage
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 53)
* Component uses 188 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 22)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 318 logical lines of code
* Class has 493 lines of code

Maybe your class should not exceed 200 lines of logical code
Too dependent information
This class looks use really high number of components.

* Efferent coupling is 25, so this class uses 25 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Too complex method code Probably bugged Too long Too dependent
ImageHistoryList
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.98 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Page\PageStore
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 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.
Probably bugged Too dependent
MediaWiki\Page\MovePage
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 77)
* Component uses 251 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 18)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 455 logical lines of code
* Class has 752 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 35, so this class uses 35 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
ImageHistoryPseudoPager
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 18)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.89 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
Article
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (33, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 207)
* Component uses 590 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 30)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 5.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 928 logical lines of code
* Class has 1437 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 35, so this class uses 35 different external components.

Maybe you should check why this class has lot of dependencies.
Blob / God object Too complex class code Too complex method code Probably bugged Too long Too dependent
WikiPage
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (86, 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 231)
* Component uses 720 operators

Maybe you should delegate some 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 7.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 1272 logical lines of code
* Class has 2520 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 40, so this class uses 40 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\Feed\FeedUtils
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.77 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Category\Category
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (16, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 37)
* 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 13)

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 long information
This class looks really long.

* Class has 240 logical lines of code
* Class has 398 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\Category\TrackingCategories
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 13)

Maybe you should delegate some code to other objects or split complex method.
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
MediaWiki\Category\CategoryViewer
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (8, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=3)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 60)
* Component uses 255 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 383 logical lines of code
* Class has 592 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
MWExceptionHandler
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (18, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=21)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* 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 12)

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 306 logical lines of code
* Class has 666 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
MWExceptionRenderer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 37)
* Component uses 129 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

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 long information
This class looks really long.

* Class has 208 logical lines of code
* Class has 332 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
UserMailer
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* Component uses 161 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 24)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.39 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 226 logical lines of code
* Class has 374 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 67)
* 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 22)

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 230 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
MediaWiki\Mail\EmailUser
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.81 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\ParamValidator\TypeDef\UserDef
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.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
MediaWiki\ParamValidator\TypeDef\TitleDef
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
FileRepo
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (67, 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 169)
* Component uses 532 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 22)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 5.09 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 951 logical lines of code
* Class has 1810 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
ForeignAPIRepo
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (17, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 63)
* Component uses 200 operators

Maybe you should delegate some 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.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 313 logical lines of code
* Class has 496 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
RepoGroup
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* Component uses 116 operators

Maybe you should delegate some 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.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 252 logical lines of code
* Class has 404 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
LocalFileMoveBatch
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 235 logical lines of code
* Class has 339 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
MediaWiki\FileRepo\File\FileSelectQueryBuilder
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
UnregisteredLocalFile
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (11, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=3)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Probably bugged warning
This component contains in theory 0.35 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Blob / God object Probably bugged
LocalFileRestoreBatch
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 49)
* 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 39)

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 221 logical lines of code
* Class has 311 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code Too complex method code Probably bugged Too long
ArchivedFile
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (29, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=3)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 56)
* Component uses 198 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 1.23 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 397 logical lines of code
* Class has 665 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
LocalFileDeleteBatch
Probably bugged warning
This component contains in theory 1.23 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 224 logical lines of code
* Class has 283 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long
LocalFile
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (51, 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 222)
* Component uses 707 operators

Maybe you should delegate some 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 7.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 1229 logical lines of code
* Class has 2056 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 41, so this class uses 41 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
OldLocalFile
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (18, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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.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 205 logical lines of code
* Class has 363 lines of code

Maybe your class should not exceed 200 lines of logical code
Blob / God object Probably bugged Too long
File
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (111, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=30)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 176)
* Component uses 637 operators

Maybe you should delegate some 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 4.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 1134 logical lines of code
* Class has 2249 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
ForeignAPIFile
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (25, 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 38)
* Component uses 112 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 0.84 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 239 logical lines of code
* Class has 366 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\FileRepo\ThumbnailEntryPoint
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 88)
* Component uses 256 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 59)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.31 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has 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 513 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
FileBackendDBRepoWrapper
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 22)
* Component uses 93 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 11)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.89 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 231 logical lines of code
* Class has 322 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
LocalRepo
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility 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 63)
* Component uses 188 operators

Maybe you should delegate some 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.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 351 logical lines of code
* Class has 531 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\Tidy\RemexCompatMunger
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 55)
* Component uses 178 operators

Maybe you should delegate some 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.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 340 logical lines of code
* Class has 478 lines of code

Maybe your class should not exceed 200 lines of logical code
Too complex class code 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\Widget\DateInputWidget
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\Widget\CheckMatrixWidget
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.41 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\HookContainer\HookContainer
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (11, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 95)
* Component uses 212 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 37)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 1.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 319 logical lines of code
* Class has 565 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\HookContainer\HookRunner
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 1)
* Component uses 499 operators

Maybe you should delegate some code to other objects.
Probably bugged warning
This component contains in theory 15.32 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too long information
This class looks really long.

* Class has 2113 logical lines of code
* Class has 2127 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 556, so this class uses 556 different external components.

Maybe you should check why this class has lot of dependencies.
Too complex class code Probably bugged Too long Too dependent
ChangeTags
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (36, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=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 99)
* Component uses 288 operators

Maybe you should delegate some code to other objects.
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 477 logical lines of code
* Class has 1081 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
ChangeTagsLogItem
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

* object has lot of public methods (9, excluding getters and setters)
* object has a high Lack of cohesion of methods (LCOM=7)
* object knows everything (and use lot of external classes)

Maybe you should reducing the number of methods splitting this object in many sub objects.
Blob / God object
MediaWiki\ChangeTags\ChangeTagsStore
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 70)
* 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 24)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 2.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 370 logical lines of code
* Class has 632 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\Site\DBSiteStore
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 12)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.4 bugs.

* Calculation is based on number of operators, operands, cyclomatic complexity
* See more details at https://en.wikipedia.org/wiki/Halstead_complexity_measures
* testsuites has dependency to this class.

Maybe you should check your unit tests for this class.
Too complex method code Probably bugged
MediaWiki\Site\SiteImporter
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
MediaWiki\Site\MediaWikiPageNameNormalizer
Too complex method code error
This class looks really complex.

* Algorithms are complex (Max cyclomatic complexity of class methods is 15)

Maybe you should delegate some code to other objects or split complex method.
Probably bugged warning
This component contains in theory 0.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
MediaWiki\Site\Site
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 long information
This class looks really long.

* Class has 232 logical lines of code
* Class has 596 lines of code

Maybe your class should not exceed 200 lines of logical code
Probably bugged Too long

Package Violations

Package Violations
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.12) than 40 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Maintenance (0.593)
* MediaWiki\Hook (0.477)
* MediaWiki\Settings (0.476)
* MediaWiki\Language (0.5)
* MediaWiki\Logger (0.152)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\Languages (0.201)
* MediaWiki\User (0.265)
* MediaWiki\StubObject (0.263)
* MediaWiki\FileRepo (0.769)
* MediaWiki\Shell (0.491)
* MediaWiki\Collation (0.281)
* Wikimedia\Rdbms (0.199)
* MediaWiki\ExternalLinks (0.444)
* MediaWiki\Permissions (0.312)
* MediaWiki\Settings\Cache (0.581)
* MediaWiki\Category (0.556)
* MediaWiki\Parser (0.43)
* MediaWiki\HookContainer (0.764)
* Wikimedia\EventRelayer (0.333)
* MediaWiki\Deferred (0.325)
* MediaWiki\FileRepo\File (0.505)
* MediaWiki (0.418)
* MediaWiki\Message (0.432)
* MediaWiki\Context (0.184)
* MediaWiki\Page (0.473)
* MediaWiki\Search (0.635)
* MediaWiki\Utils (0.386)
* MediaWiki\Session (0.562)
* MediaWiki\Revision (0.346)
* MediaWiki\Parser\Parsoid (0.753)
* MediaWiki\Installer (0.926)
* MediaWiki\User\TempUser (0.491)
* MediaWiki\RenameUser (0.667)
* MediaWiki\Pager (0.81)
* Wikimedia\Diff (0.462)
* MediaWiki\SiteStats (0.5)
* MediaWiki\Composer (0.889)
* MediaWiki\Auth (0.75)
* MediaWiki\Linker (0.312)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Maintenance
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.593) than 18 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Storage (0.73)
* MediaWiki\DAO (0.625)
* MediaWiki\RenameUser (0.667)
* MediaWiki\Installer (0.926)
* MediaWiki\Site (0.762)
* MediaWiki\Deferred\LinksUpdate (0.864)
* MediaWiki\Settings\Source (0.684)
* MediaWiki\DB (0.65)
* MediaWiki\Feed (0.636)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Page\File (0.6)
* MediaWiki\JobQueue (0.636)
* MediaWiki\FileRepo (0.769)
* MediaWiki\Block (0.729)
* MediaWiki\Rest\Handler\Helper (0.844)
* MediaWiki\Skin (0.74)
* MediaWiki\ParamValidator\TypeDef (0.816)
* MediaWiki\Tidy (0.667)
Stable Dependencies Principle
MediaWiki\Message
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.432) than 6 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Page (0.473)
* MediaWiki\Language (0.5)
* MediaWiki\Output (0.643)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\Api (0.696)
* MediaWiki\FileRepo\File (0.505)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Logger
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.152) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Message (0.432)
* MediaWiki (0.418)
* Wikimedia\Rdbms (0.199)
* MediaWiki\Logger\Monolog (0.938)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Request
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.26) than 9 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Session (0.562)
* MediaWiki (0.418)
* MediaWiki\Parser (0.43)
* MediaWiki\Http (0.6)
* MediaWiki\Message (0.432)
* MediaWiki\Hook (0.477)
* MediaWiki\User (0.265)
* Wikimedia\Stats (0.442)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\PoolCounter
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.727) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Parser\Parsoid (0.753)
Stable Dependencies Principle
MediaWiki\Hook
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.477) than 38 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\PoolCounter (0.727)
* MediaWiki\Language (0.5)
* MediaWiki\ChangeTags (0.68)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Sparql (0.75)
* MediaWiki\Storage (0.73)
* MediaWiki\Feed (0.636)
* MediaWiki\Pager (0.81)
* MediaWiki\Content\Transform (0.491)
* MediaWiki\Diff\Hook (0.769)
* MediaWiki\Diff\TextDiffer (0.867)
* MediaWiki\Search\SearchWidgets (0.691)
* MediaWiki\Search (0.635)
* MediaWiki\Parser\Parsoid (0.753)
* MediaWiki\Content\Hook (0.697)
* MediaWiki\OutputTransform (0.628)
* MediaWiki\FileRepo\File (0.505)
* MediaWiki\JobQueue (0.636)
* MediaWiki\Deferred\LinksUpdate (0.864)
* MediaWiki\Actions (0.935)
* MediaWiki\Skin (0.74)
* Wikimedia\Http (0.5)
* MediaWiki\Languages\Data (0.75)
* MediaWiki\Api (0.696)
* MediaWiki\CommentFormatter (0.527)
* MediaWiki\Logging (0.875)
* MediaWiki\Shell (0.491)
* Wikimedia\ParamValidator\TypeDef (0.571)
* MediaWiki\User\TempUser (0.491)
* MediaWiki\Api\Hook (0.686)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\Block (0.729)
* MediaWiki\Session (0.562)
* MediaWiki\DB (0.65)
* MediaWiki\DAO (0.625)
* MediaWiki\Watchlist (0.514)
* MediaWiki\Mail (0.806)
* MediaWiki\ParamValidator\TypeDef (0.816)
Stable Dependencies Principle
MediaWiki\Content\Renderer
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.273) than 5 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Page (0.473)
* MediaWiki\Hook (0.477)
* MediaWiki\Content (0.387)
* Wikimedia\UUID (0.333)
* MediaWiki\Parser (0.43)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Content
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.387) than 10 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Page (0.473)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Hook (0.477)
* MediaWiki (0.418)
* MediaWiki\Content\Hook (0.697)
* MediaWiki\Parser (0.43)
* MediaWiki\Parser\Parsoid (0.753)
* MediaWiki\Content\Transform (0.491)
* MediaWiki\Search\SearchWidgets (0.691)
* MediaWiki\Language (0.5)
Stable Dependencies Principle
MediaWiki\Content\Transform
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.491) than 3 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Content\Hook (0.697)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Search\SearchWidgets (0.691)
Stable Dependencies Principle
MediaWiki\Content\Hook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.697) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Diff\Hook (0.769)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Deferred
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.325) than 10 package(s) that it depends on.
The packages that are more stable are

* MediaWiki (0.418)
* MediaWiki\Page (0.473)
* MediaWiki\Revision (0.346)
* MediaWiki\Storage (0.73)
* Wikimedia\Mime (0.467)
* MediaWiki\Search\SearchWidgets (0.691)
* MediaWiki\Auth (0.75)
* MediaWiki\HookContainer (0.764)
* MediaWiki\SiteStats (0.5)
* MediaWiki\Hook (0.477)
Stable Dependencies Principle
MediaWiki\OutputTransform
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.628) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Tidy (0.667)
* MediaWiki\OutputTransform\Stages (0.957)
* MediaWiki\Parser\Parsoid (0.753)
Stable Dependencies Principle
MediaWiki\Config
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.108) than 3 package(s) that it depends on.
The packages that are more stable are

* global (0.12)
* Wikimedia\Http (0.5)
* Wikimedia\Diff (0.462)
Stable Abstractions Principle Stable Dependencies Principle
Wikimedia\Message
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.057) than 3 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\MessageFormatter (0.091)
* global (0.12)
* Wikimedia\NonSerializable (0.066)
Stable Abstractions Principle Stable Dependencies Principle
Wikimedia\EventRelayer
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.333) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\FileBackend\FSFile (0.718)
* Wikimedia\Diff (0.462)
Stable Dependencies Principle
Wikimedia\Composer
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Wikimedia\UUID
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
MediaWiki\Libs
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Wikimedia\Stats
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.442) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\Stats\Metrics (0.6)
Stable Dependencies Principle
Wikimedia\Stats\Emitters
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.368) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\Stats (0.442)
Stable Dependencies Principle
Wikimedia\Stats\Formatters
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.333) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\Stats\Metrics (0.6)
Stable Dependencies Principle
Wikimedia\Reflection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Wikimedia\Rdbms
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.199) than 6 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\Rdbms\Platform (0.667)
* Wikimedia\Rdbms\Replication (0.7)
* Wikimedia\Diff (0.462)
* Wikimedia\Stats\Emitters (0.368)
* Wikimedia\Stats\Exceptions (0.333)
* Wikimedia\EventRelayer (0.333)
Stable Abstractions Principle Stable Dependencies Principle
Wikimedia\Rdbms\Database
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.111) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\Rdbms (0.199)
Stable Dependencies Principle
Wikimedia
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.07) than 2 package(s) that it depends on.
The packages that are more stable are

* global (0.12)
* MediaWiki\Libs (0.148)
Stable Abstractions Principle Stable Dependencies Principle
Wikimedia\NonSerializable
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.066) than 2 package(s) that it depends on.
The packages that are more stable are

* global (0.12)
* MediaWiki\Message (0.432)
Stable Dependencies Principle
Wikimedia\ParamValidator
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.345) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\ParamValidator\Util (0.571)
Stable Dependencies Principle
Wikimedia\ParamValidator\TypeDef
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.571) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\ParamValidator\Util (0.571)
Stable Dependencies Principle
Wikimedia\Mime
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.467) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Hook (0.477)
* MediaWiki\Page (0.473)
* MediaWiki\Http (0.6)
* MediaWiki\FileBackend\FSFile (0.718)
Stable Dependencies Principle
MediaWiki\JobQueue
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.636) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Skin (0.74)
* MediaWiki\Mail (0.806)
* MediaWiki\Storage (0.73)
* MediaWiki\Api\Validator (0.889)
Stable Dependencies Principle
MediaWiki\Languages
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.201) than 8 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki (0.418)
* MediaWiki\Profiler (0.324)
* MediaWiki\Language (0.5)
* MediaWiki\User (0.265)
* MediaWiki\Utils (0.386)
* MediaWiki\Collation (0.281)
* MediaWiki\Hook (0.477)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Language
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.5) than 6 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Block (0.729)
* MediaWiki\Api (0.696)
* MediaWiki\Pager (0.81)
* MediaWiki\CommentFormatter (0.527)
* MediaWiki\Api\Hook (0.686)
Stable Dependencies Principle
MediaWiki\Pager
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.81) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Navigation (0.875)
* MediaWiki\Actions (0.935)
Stable Dependencies Principle
MediaWiki
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.418) than 50 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Hook (0.477)
* MediaWiki\FileRepo\File (0.505)
* MediaWiki\Output (0.643)
* Wikimedia\Mime (0.467)
* MediaWiki\Shell (0.491)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Interwiki (0.636)
* MediaWiki\Actions (0.935)
* MediaWiki\Auth (0.75)
* MediaWiki\Block (0.729)
* MediaWiki\Page\File (0.6)
* MediaWiki\Storage (0.73)
* MediaWiki\User\CentralId (0.684)
* MediaWiki\ChangeTags (0.68)
* MediaWiki\CommentFormatter (0.527)
* MediaWiki\Settings\Config (0.583)
* MediaWiki\Page (0.473)
* MediaWiki\Content\Transform (0.491)
* MediaWiki\Parser (0.43)
* MediaWiki\Edit (0.818)
* MediaWiki\OutputTransform (0.628)
* MediaWiki\Mail (0.806)
* MediaWiki\FileBackend\LockManager (0.933)
* MediaWiki\Language (0.5)
* MediaWiki\Parser\Parsoid (0.753)
* MediaWiki\Http (0.6)
* MediaWiki\EditPage (0.882)
* MediaWiki\JobQueue (0.636)
* MediaWiki\Rest\Handler\Helper (0.844)
* MediaWiki\Parser\Parsoid\Config (0.852)
* MediaWiki\Installer (0.926)
* MediaWiki\PoolCounter (0.727)
* MediaWiki\Preferences (0.921)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\Search\SearchWidgets (0.691)
* MediaWiki\Search (0.635)
* MediaWiki\Site (0.762)
* MediaWiki\DB (0.65)
* Wikimedia\Stats (0.442)
* MediaWiki\FileBackend\FSFile (0.718)
* MediaWiki\User\TempUser (0.491)
* MediaWiki\Tidy (0.667)
* MediaWiki\Category (0.556)
* MediaWiki\User\Options (0.462)
* MediaWiki\User\Registration (0.714)
* MediaWiki\Watchlist (0.514)
* MediaWiki\Export (0.692)
* Wikimedia\WRStats (0.5)
* MediaWiki\Search\Entity (0.606)
* MediaWiki\Message (0.432)
Stable Dependencies Principle
MediaWiki\Title
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.116) than 19 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Linker (0.312)
* MediaWiki\Page (0.473)
* MediaWiki\Hook (0.477)
* MediaWiki (0.418)
* Wikimedia\Rdbms (0.199)
* global (0.12)
* MediaWiki\Parser (0.43)
* MediaWiki\Libs (0.148)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Request (0.26)
* MediaWiki\Deferred (0.325)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\JobQueue (0.636)
* MediaWiki\Utils (0.386)
* MediaWiki\Context (0.184)
* MediaWiki\Html (0.206)
* MediaWiki\Languages (0.201)
* MediaWiki\Interwiki (0.636)
* MediaWiki\Message (0.432)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\EditPage
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.882) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\EditPage\Constraint (0.966)
Stable Dependencies Principle
MediaWiki\ResourceLoader
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.829) than 1 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\DependencyStore (0.833)
Stable Dependencies Principle
MediaWiki\ResourceLoader\Hook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.75) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\ResourceLoader (0.829)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\RenameUser\Hook
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.5) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\RenameUser (0.667)
Stable Dependencies Principle
MediaWiki\RenameUser
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.667) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Block
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.729) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\ExternalLinks
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.444) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Hook (0.477)
Stable Dependencies Principle
MediaWiki\User
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.265) than 20 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Utils (0.386)
* MediaWiki\Auth (0.75)
* MediaWiki\HookContainer (0.764)
* MediaWiki\User\Options (0.462)
* MediaWiki\Parser (0.43)
* MediaWiki\Message (0.432)
* MediaWiki\Deferred (0.325)
* MediaWiki\User\TempUser (0.491)
* MediaWiki\User\CentralId (0.684)
* MediaWiki\Settings\Cache (0.581)
* MediaWiki\Hook (0.477)
* MediaWiki\Permissions (0.312)
* MediaWiki\Block (0.729)
* MediaWiki (0.418)
* MediaWiki\JobQueue (0.636)
* MediaWiki\DAO (0.625)
* MediaWiki\Session (0.562)
* MediaWiki\Mail (0.806)
* MediaWiki\Page (0.473)
* MediaWiki\Revision (0.346)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\User\CentralId
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.684) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Block (0.729)
Stable Dependencies Principle
MediaWiki\User\Options
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.462) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\HTMLForm (0.567)
* MediaWiki\DB (0.65)
* MediaWiki\User\Registration (0.714)
Stable Dependencies Principle
MediaWiki\User\TempUser
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.491) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Auth (0.75)
* MediaWiki\User\CentralId (0.684)
* MediaWiki\Session (0.562)
* Wikimedia\Rdbms\Platform (0.667)
Stable Dependencies Principle
MediaWiki\Permissions
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.312) than 12 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Page (0.473)
* Wikimedia\EventRelayer (0.333)
* MediaWiki\Block (0.729)
* MediaWiki\User\TempUser (0.491)
* MediaWiki\Actions (0.935)
* MediaWiki (0.418)
* MediaWiki\Message (0.432)
* MediaWiki\Session (0.562)
* Wikimedia\WRStats (0.5)
* Wikimedia\Stats\Emitters (0.368)
* MediaWiki\Category (0.556)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Permissions\Hook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
MediaWiki\Auth
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.75) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Status
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.101) than 8 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Hook (0.477)
* MediaWiki\Language (0.5)
* global (0.12)
* MediaWiki\Message (0.432)
* MediaWiki\Context (0.184)
* MediaWiki (0.418)
* MediaWiki\User (0.265)
* Wikimedia\Rdbms (0.199)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Output
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.643) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\FileBackend\FSFile (0.718)
* MediaWiki\Skin (0.74)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\DB (0.65)
Stable Dependencies Principle
MediaWiki\CommentFormatter
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.527) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Parser
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.43) than 18 package(s) that it depends on.
The packages that are more stable are

* Wikimedia\Stats (0.442)
* MediaWiki\Hook (0.477)
* MediaWiki\Parser\Parsoid (0.753)
* MediaWiki\Tidy (0.667)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Page (0.473)
* MediaWiki\Page\File (0.6)
* MediaWiki\User\Options (0.462)
* MediaWiki\Http (0.6)
* MediaWiki\Category (0.556)
* MediaWiki\Preferences (0.921)
* MediaWiki\CommentFormatter (0.527)
* MediaWiki\Language (0.5)
* MediaWiki\Content\Hook (0.697)
* MediaWiki\FileRepo\File (0.505)
* MediaWiki\Output (0.643)
* MediaWiki\Edit (0.818)
* MediaWiki\SiteStats (0.5)
Stable Dependencies Principle
MediaWiki\Parser\Parsoid
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.753) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Parser\Parsoid\Config (0.852)
* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Profiler
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.324) than 3 package(s) that it depends on.
The packages that are more stable are

* MediaWiki (0.418)
* MediaWiki\Parser (0.43)
* Wikimedia\DebugInfo (0.75)
Stable Dependencies Principle
MediaWiki\Context
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.184) than 12 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Request (0.26)
* MediaWiki\Page (0.473)
* MediaWiki (0.418)
* MediaWiki\Output (0.643)
* MediaWiki\User (0.265)
* MediaWiki\Permissions (0.312)
* MediaWiki\DB (0.65)
* MediaWiki\Language (0.5)
* MediaWiki\Session (0.562)
* Wikimedia\Stats (0.442)
* MediaWiki\HookContainer (0.764)
* MediaWiki\StubObject (0.263)
Stable Dependencies Principle
MediaWiki\Settings
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.476) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Settings\Source (0.684)
* MediaWiki\Hook (0.477)
* MediaWiki\Settings\Config (0.583)
* MediaWiki\Settings\Cache (0.581)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Settings\Source
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.684) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Settings\Source\Format (0.75)
Stable Dependencies Principle
MediaWiki\Settings\Cache
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.581) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Settings\Source (0.684)
Stable Dependencies Principle
MediaWiki\Utils
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.386) than 11 package(s) that it depends on.
The packages that are more stable are

* MediaWiki (0.418)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Language (0.5)
* MediaWiki\Message (0.432)
* MediaWiki\Shell (0.491)
* Wikimedia\Mime (0.467)
* MediaWiki\FileRepo\File (0.505)
* MediaWiki\Hook (0.477)
* MediaWiki\Settings\Cache (0.581)
* MediaWiki\DAO (0.625)
* MediaWiki\Category (0.556)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\HTMLForm
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.567) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HTMLForm\Field (0.983)
Stable Dependencies Principle
MediaWiki\Revision
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.346) than 11 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Content (0.387)
* MediaWiki\Page (0.473)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Storage (0.73)
* MediaWiki\Hook (0.477)
* MediaWiki\Parser (0.43)
* MediaWiki (0.418)
* MediaWiki\Utils (0.386)
* MediaWiki\Content\Transform (0.491)
* Wikimedia\Rdbms\Platform (0.667)
* MediaWiki\DAO (0.625)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Shell
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.491) than 3 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Http (0.6)
* MediaWiki\HookContainer (0.764)
* Wikimedia\Http (0.5)
Stable Dependencies Principle
MediaWiki\Watchlist
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.514) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* Wikimedia\ParamValidator\TypeDef (0.571)
Stable Dependencies Principle
MediaWiki\Json
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.085) than 2 package(s) that it depends on.
The packages that are more stable are

* global (0.12)
* MediaWiki\Status (0.101)
Stable Dependencies Principle
MediaWiki\DB
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.65) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\ResourceLoader (0.829)
* MediaWiki\Skin (0.74)
Stable Dependencies Principle
MediaWiki\Skins\Hook
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.5) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\ResourceLoader (0.829)
Stable Dependencies Principle
MediaWiki\Skin
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.74) than 4 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\ResourceLoader (0.829)
* MediaWiki\ParamValidator\TypeDef (0.816)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Api\Validator (0.889)
Stable Dependencies Principle
MediaWiki\Diff\Hook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.769) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Diff\TextDiffer (0.867)
* MediaWiki\Pager (0.81)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Rest
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.689) than 7 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Rest\Validator (0.75)
* MediaWiki\Api (0.696)
* MediaWiki\Storage (0.73)
* MediaWiki\EditPage (0.882)
* MediaWiki\Api\Validator (0.889)
* MediaWiki\Auth (0.75)
Stable Dependencies Principle
MediaWiki\Rest\Reporter
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.6) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Rest (0.689)
Stable Dependencies Principle
MediaWiki\Rest\HeaderParser
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
MediaWiki\Rest\BasicAccess
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.5) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Rest (0.689)
Stable Dependencies Principle
MediaWiki\Api
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.696) than 7 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\EditPage (0.882)
* MediaWiki\Api\Validator (0.889)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\Skin (0.74)
* MediaWiki\Block (0.729)
* MediaWiki\Auth (0.75)
Stable Dependencies Principle
MediaWiki\Api\Hook
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.686) than 13 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Api (0.696)
* MediaWiki\Block (0.729)
* MediaWiki\Storage (0.73)
* MediaWiki\Skin (0.74)
* MediaWiki\Auth (0.75)
* MediaWiki\Api\Validator (0.889)
* MediaWiki\PoolCounter (0.727)
* MediaWiki\EditPage (0.882)
* MediaWiki\Preferences (0.921)
* MediaWiki\Pager (0.81)
* MediaWiki\Diff\TextDiffer (0.867)
* MediaWiki\Rest (0.689)
Stable Dependencies Principle
MediaWiki\DAO
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.625) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Storage (0.73)
* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Session
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.562) than 3 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Settings\Cache (0.581)
* MediaWiki\Api\Hook (0.686)
Stable Dependencies Principle
MediaWiki\CommentStore
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.246) than 6 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Message (0.432)
* MediaWiki\Language (0.5)
* MediaWiki (0.418)
* MediaWiki\Page (0.473)
* MediaWiki\Revision (0.346)
* MediaWiki\Linker (0.312)
Stable Dependencies Principle
MediaWiki\StubObject
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.263) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\User (0.265)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Html
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.206) than 13 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Tidy (0.667)
* MediaWiki\Request (0.26)
* MediaWiki\Output (0.643)
* MediaWiki (0.418)
* MediaWiki\Utils (0.386)
* MediaWiki\CommentStore (0.246)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Revision (0.346)
* MediaWiki\Hook (0.477)
* MediaWiki\Page (0.473)
* MediaWiki\Language (0.5)
* MediaWiki\Message (0.432)
* MediaWiki\Export (0.692)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Export
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.692) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Linker
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.312) than 9 package(s) that it depends on.
The packages that are more stable are

* MediaWiki (0.418)
* Wikimedia\EventRelayer (0.333)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Parser (0.43)
* MediaWiki\Revision (0.346)
* MediaWiki\Message (0.432)
* MediaWiki\Permissions (0.312)
* MediaWiki\Hook (0.477)
* MediaWiki\Shell (0.491)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Collation
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.281) than 6 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Hook (0.477)
* Wikimedia\Diff (0.462)
* MediaWiki\Parser (0.43)
* MediaWiki (0.418)
* MediaWiki\Utils (0.386)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Search
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.635) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Search\SearchWidgets (0.691)
Stable Dependencies Principle
MediaWiki\Search\SearchWidgets
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.691) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Search\Entity
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.606) than 3 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Search\SearchWidgets (0.691)
* MediaWiki\Search (0.635)
* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\WikiMap
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.075) than 3 package(s) that it depends on.
The packages that are more stable are

* MediaWiki (0.418)
* MediaWiki\Linker (0.312)
* Wikimedia\Rdbms (0.199)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\Storage
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.73) than 5 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Parser\Parsoid (0.753)
* MediaWiki\Edit (0.818)
* MediaWiki\Deferred\LinksUpdate (0.864)
* MediaWiki\ResourceLoader (0.829)
Stable Dependencies Principle
MediaWiki\Interwiki
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.636) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
* MediaWiki\Site (0.762)
Stable Dependencies Principle
MediaWiki\Page
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.473) than 22 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Hook (0.477)
* MediaWiki\EditPage (0.882)
* MediaWiki\HookContainer (0.764)
* MediaWiki\Storage (0.73)
* MediaWiki\Language (0.5)
* MediaWiki\JobQueue (0.636)
* MediaWiki\Deferred\LinksUpdate (0.864)
* MediaWiki\ResourceLoader (0.829)
* MediaWiki\PoolCounter (0.727)
* MediaWiki\Parser\Parsoid (0.753)
* MediaWiki\HTMLForm (0.567)
* MediaWiki\FileRepo\File (0.505)
* MediaWiki\Skin (0.74)
* MediaWiki\DAO (0.625)
* MediaWiki\Category (0.556)
* MediaWiki\Page\Hook (0.833)
* MediaWiki\Interwiki (0.636)
* MediaWiki\Content\Transform (0.491)
* MediaWiki\Pager (0.81)
* MediaWiki\Page\File (0.6)
* MediaWiki\Output (0.643)
* MediaWiki\Actions (0.935)
Stable Dependencies Principle
MediaWiki\Page\Hook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
MediaWiki\Page\File
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.6) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\Mail
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.806) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Preferences (0.921)
Stable Dependencies Principle
MediaWiki\Mail\Hook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.8) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Mail (0.806)
Stable Abstractions Principle Stable Dependencies Principle
MediaWiki\FileRepo\File
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.505) than 5 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\FileRepo (0.769)
* MediaWiki\ParamValidator\TypeDef (0.816)
* MediaWiki\Deferred\LinksUpdate (0.864)
* MediaWiki\JobQueue (0.636)
* MediaWiki\PoolCounter (0.727)
Stable Dependencies Principle
MediaWiki\FileRepo
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.769) than 1 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\ParamValidator\TypeDef (0.816)
Stable Dependencies Principle
MediaWiki\Widget
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
MediaWiki\HookContainer
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.764) than 7 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\ChangeTags\Hook (0.824)
* MediaWiki\Diff\Hook (0.769)
* MediaWiki\Mail\Hook (0.8)
* MediaWiki\Page\Hook (0.833)
* MediaWiki\Diff\TextDiffer (0.867)
* MediaWiki\Mail (0.806)
* MediaWiki\ResourceLoader (0.829)
Stable Dependencies Principle
MediaWiki\ChangeTags
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

This package is more stable (0.68) than 2 package(s) that it depends on.
The packages that are more stable are

* MediaWiki\Storage (0.73)
* MediaWiki\HookContainer (0.764)
Stable Dependencies Principle
MediaWiki\ChangeTags\Hook
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle