Created at 2026-10-13 17:48:57 , with PHPMetrics 2.11.0 (Jean-François Lépine).
Violations
188
Information
18
Warnings
133
Errors
37
Criticals
0

Class Violations

Class Violations
Stewart\Support\State\IndexedRegistry
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.
Blob / God object
Stewart\Support\Stream\ThresholdCrossingOperator
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
Stewart\Support\Stream\ComposedStateChangeStream
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
Stewart\Codegen\Snapshot\SnapshotCodec
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.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
Stewart\Codegen\Attribute\AttributeCatalog
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
Stewart\Codegen\Service\ServiceSelector
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
Stewart\Codegen\Console\GenerateCommand
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 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.
Probably bugged Too dependent
Stewart\Codegen\Model\GenerationModelFactory
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 dependent
Stewart\Store\Redis\RedisStoreBackend
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
Stewart\Sun\NoaaSolarCalculator
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.
Probably bugged
Stewart\Mqtt\Connection\MqttConnection
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
Stewart\Mqtt\ReconnectingMqttLink
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
Stewart\Client\State\EntityStateDecoder
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
Stewart\Client\HaClient
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=3)
* object knows everything (and use lot of external classes)

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

* Algorithms are complex (Total cyclomatic complexity of class is 64)
* Component uses 146 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 334 logical lines of code
* Class has 381 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 74, so this class uses 74 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
Stewart\Client\Connection\HaConnection
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 class code error
This class looks really complex.

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

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

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

* Class has 259 logical lines of code
* Class has 275 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
Stewart\Client\HaConfig
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
Stewart\Client\Component\ComponentEventDecoder
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
Stewart\Client\Component\ExposedEntitySnapshotReader
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
Stewart\Client\Event\EventDecoder
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
Stewart\Runtime\Control\SnapshotAssembler
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
Stewart\Runtime\Control\Server\ControlServer
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
Stewart\Runtime\Dispatch\LocalDispatcher
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 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.
Probably bugged Too dependent
Stewart\Runtime\Dispatch\SubscriptionQueue
Probably bugged warning
This component contains in theory 0.44 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
Stewart\Runtime\Ipc\Wire\IpcCodec
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 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 Too dependent
Stewart\Runtime\Config\ConfigSection
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

Maybe you should delegate some code to other objects.
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 class code Probably bugged
Stewart\Runtime\Config\StewartConfigSchema
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
Stewart\Runtime\Config\EnvironmentOverlay
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
Stewart\Runtime\App\AppCatalogResolver
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
Stewart\Runtime\App\AppDiscovery
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
Stewart\Runtime\Console\RunCommand
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
Stewart\Runtime\Console\StatusRenderer
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.
Probably bugged
Stewart\Runtime\Console\DoctorCommand
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
Stewart\Runtime\Json\StringIdentifierConverter
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.
Blob / God object
Stewart\Runtime\Json\WireMapper
Too complex class code error
This class looks really complex.

* Algorithms are complex (Total cyclomatic complexity of class is 44)
* Component uses 96 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 complex class code Probably bugged
Stewart\Runtime\Json\ClassShapeReader
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
Stewart\Runtime\Schedule\WorkerScheduler
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
Stewart\Runtime\Schedule\ScheduleEntry
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
Stewart\Runtime\Broker\Exposure\ExposureLink
Too complex class code error
This class looks really complex.

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

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

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

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

* Class has 261 logical lines of code
* Class has 280 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 Probably bugged Too long Too dependent
Stewart\Runtime\Broker\WorkerHandle
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 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
Stewart\Runtime\Broker\AppRunningTotals
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
Stewart\Runtime\Broker\BrokerHaEvents
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 dependent
Stewart\Runtime\Broker\WorkerPool
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 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.
Probably bugged Too dependent
Stewart\Runtime\Broker\WebsocketHaSession
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 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.
Probably bugged Too dependent
Stewart\Runtime\Container\AppOptionResolver
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
Stewart\Runtime\Container\AppContainerBuilder
Probably bugged warning
This component contains in theory 0.79 bugs.

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

Maybe you should check your unit tests for this class.
Probably bugged
Stewart\Runtime\Worker\WorkerHaContext
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 dependent information
This class looks use really high number of components.

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

Maybe you should check why this class has lot of dependencies.
Blob / God object Too dependent
Stewart\Runtime\Worker\WorkerEntityExposure
Too dependent information
This class looks use really high number of components.

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

Maybe you should check why this class has lot of dependencies.
Too dependent
Stewart\Runtime\Worker\AppLifecycle
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
Stewart\Contracts\State\Collection\EntityStateCollection
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
Stewart\Contracts\Time\Instant
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.
Blob / God object
Stewart\Contracts\Time\Duration
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
Stewart\Contracts\Selector\Selector
Blob / God object error
A blob object (or "god class") does not follow the Single responsibility principle.

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

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

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

Maybe you should delegate some 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.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.
Blob / God object Too complex class code Too complex method code Probably bugged
Stewart\Contracts\Collection\TypedCollection
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
Stewart\Contracts\Trigger\HaTrigger
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=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.
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.
Blob / God object Probably bugged
Stewart\Contracts\Schedule\TimeOfDay
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.
Blob / God object
Stewart\Contracts\Registry\EntityFilter
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=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.
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
Stewart\Contracts\Registry\Update\EntityRegistryUpdate
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=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.
Blob / God object Too complex method code

Package Violations

Package Violations
Stewart\Store\Exception
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Support\State\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Support\Url
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Support\Wire
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

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

* Stewart\Contracts\Exception (0.08)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Support\Text
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Support\Json
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Support\Secret
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Codegen\Snapshot
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Client (0.88)
* Stewart\Client\Connection (0.838)
* Stewart\Client\Registry (0.875)
Stable Dependencies Principle
Stewart\Codegen\Output
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.188) than 2 package(s) that it depends on.
The packages that are more stable are

* Stewart\Codegen\Output\Collection (0.4)
* Stewart\Codegen\Emitter (0.625)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Codegen\Output\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Codegen\Attribute
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

* Stewart\Codegen\Model (0.595)
Stable Dependencies Principle
Stewart\Codegen\Attribute\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

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

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

* Stewart\Codegen\Snapshot (0.741)
* Stewart\Codegen\Entity (0.667)
Stable Dependencies Principle
Stewart\Codegen\Service
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

* Stewart\Codegen\Snapshot (0.741)
Stable Dependencies Principle
Stewart\Codegen\Service\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Codegen\Emitter
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Codegen (0.667)
Stable Dependencies Principle
Stewart\Codegen\Exception
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Codegen\Entity
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

* Stewart\Codegen\Snapshot (0.741)
Stable Dependencies Principle
Stewart\Codegen\Model
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Codegen\Entity (0.667)
* Stewart\Codegen\Service (0.6)
* Stewart\Codegen\Snapshot (0.741)
* Stewart\Codegen (0.667)
Stable Dependencies Principle
Stewart\Codegen\Model\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Codegen\Php
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Mqtt\Exception
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

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

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

* Stewart\Client\Connection\Command\Component (0.9)
Stable Dependencies Principle
Stewart\Client\Connection\Command
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Registry\Update (0.5)
* Stewart\Contracts\History (0.563)
Stable Dependencies Principle
Stewart\Client\Exception
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Client\Component\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\State
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Support\State (0.652)
* Stewart\Runtime\Registry (0.533)
Stable Dependencies Principle
Stewart\Runtime\Metrics
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Control (0.917)
Stable Dependencies Principle
Stewart\Runtime\Metrics\Exposition
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\Control\Request
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Control (0.917)
* Stewart\Runtime\Admin (0.786)
Stable Dependencies Principle
Stewart\Runtime\Control
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Control\Server (0.95)
Stable Dependencies Principle
Stewart\Runtime\Control\Protocol\Status
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\Control\Protocol\Frame
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.071) than 1 package(s) that it depends on.
The packages that are more stable are

* Stewart\Runtime\Control\Protocol\Status (0.275)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Dispatch
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Support\Stream (0.722)
Stable Dependencies Principle
Stewart\Runtime\Ipc\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.341) than 5 package(s) that it depends on.
The packages that are more stable are

* Stewart\Runtime\Ipc\Wire (0.667)
* Stewart\Contracts\History (0.563)
* Stewart\Contracts\Registry\Update (0.5)
* Stewart\Contracts\Registry (0.436)
* Stewart\Contracts\Exposure\Command (0.417)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Ipc
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Ipc\Wire (0.667)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Ipc\Wire\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\Ipc\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\Health
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Control (0.917)
Stable Dependencies Principle
Stewart\Runtime\Time
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

* Stewart\Support\Schedule (0.773)
Stable Dependencies Principle
Stewart\Runtime\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.402) than 5 package(s) that it depends on.
The packages that are more stable are

* Stewart\Runtime\Logging (0.565)
* Stewart\Client\Connection (0.838)
* Stewart\Runtime\Config\Environment (0.667)
* Stewart\Store (0.667)
* Stewart\Client\Component (0.69)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Config\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

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

* Stewart\Contracts\Exception (0.08)
* Stewart\Contracts\App\Collection (0.125)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Scope
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

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

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\Console
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Kernel (0.96)
Stable Dependencies Principle
Stewart\Runtime\Model
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Exception (0.08)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Model\Collection
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.1) than 1 package(s) that it depends on.
The packages that are more stable are

* Stewart\Contracts\Collection (0.13)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Json\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\Schedule
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Worker\Context (0.921)
Stable Dependencies Principle
Stewart\Runtime\Broker
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Broker\Deploy (0.889)
* Stewart\Runtime\Broker\Message (0.972)
* Stewart\Runtime\Broker\Trigger (0.833)
* Stewart\Client (0.88)
* Stewart\Runtime\Broker\Component (0.8)
Stable Dependencies Principle
Stewart\Runtime\Broker\Mqtt
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Broker (0.792)
Stable Dependencies Principle
Stewart\Runtime\Broker\Http\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Runtime\Broker\Exposure
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Client (0.88)
* Stewart\Runtime\Broker\Component (0.8)
* Stewart\Runtime\Broker (0.792)
Stable Dependencies Principle
Stewart\Runtime\Broker\Collection
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.375) than 1 package(s) that it depends on.
The packages that are more stable are

* Stewart\Runtime\Broker (0.792)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Runtime\Broker\Trigger
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Client (0.88)
Stable Dependencies Principle
Stewart\Runtime\Broker\Component
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

* Stewart\Client (0.88)
Stable Dependencies Principle
Stewart\Runtime\Worker
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Worker\Message (0.957)
* Stewart\Sun (0.917)
* Stewart\Runtime\Worker\Context (0.921)
* Stewart\Runtime\Worker\Exposure (0.934)
* Stewart\Runtime\Worker\Registry (0.917)
* Stewart\Runtime\Container (0.909)
Stable Dependencies Principle
Stewart\Runtime\Admin
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Runtime\Broker (0.792)
* Stewart\Runtime\Control\Assembler (0.875)
Stable Dependencies Principle
Stewart\Runtime\Registry
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Support\State (0.652)
Stable Dependencies Principle
Stewart\Contracts\State
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 1 package(s) that it depends on.
The packages that are more stable are

* Stewart\Contracts\Entity (0.204)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\State\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Registry (0.436)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\Mqtt
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts (0.186)
Stable Dependencies Principle
Stewart\Contracts
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Entity (0.204)
* Stewart\Contracts\History (0.563)
* Stewart\Contracts\State\Collection (0.333)
* Stewart\Contracts\Registry (0.436)
Stable Dependencies Principle
Stewart\Contracts\Sun
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Contracts\Exposure
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts (0.186)
* Stewart\Contracts\Schedule (0.32)
* Stewart\Contracts\Exposure\Action (0.615)
* Stewart\Contracts\Entity (0.204)
Stable Dependencies Principle
Stewart\Contracts\Service
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Entity (0.204)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\Time
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Exception (0.08)
Stable Dependencies Principle
Stewart\Contracts\Exception
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.08) than 2 package(s) that it depends on.
The packages that are more stable are

* Stewart\Contracts\Entity (0.204)
* Stewart\Contracts\Exposure (0.156)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\Selector\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Contracts\Selector
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Selector\Collection (0.4)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\App
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.033) than 1 package(s) that it depends on.
The packages that are more stable are

* Stewart\Contracts\Exception (0.08)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\App\Collection
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.125) than 1 package(s) that it depends on.
The packages that are more stable are

* Stewart\Contracts\Collection (0.13)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\Entity
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\History (0.563)
Stable Dependencies Principle
Stewart\Contracts\Entity\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Collection (0.13)
Stable Abstractions Principle Stable Dependencies Principle
Stewart\Contracts\Trigger
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Contracts\Trigger\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Contracts\Event
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Contracts\Topic
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Contracts\History\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Abstractions Principle
Stewart\Contracts\Registry
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Registry\Update (0.5)
Stable Dependencies Principle
Stewart\Contracts\Registry\Collection
Stable Abstractions Principle warning
Packages should be either abstract and stable or concrete and instable.

This package is instable and abstract.
Stable Dependencies Principle warning
Packages should depend in the direction of stability.

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

* Stewart\Contracts\Registry (0.436)
Stable Abstractions Principle Stable Dependencies Principle