Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class, interface, enum, or trait `Psr\Log\LogLevel` not found. >`Psr\Log\LogLevel` is not defined or cannot be found Help: Ensure the name is correct, including its namespace, and that it's properly defined and autoloadable.

Class has high complexity. >Class has a cyclomatic complexity of 28, which exceeds the threshold of 15.

Parameter list is too long. >This list has 6 parameters, which exceeds the threshold of 5. Having a large number of parameters can make functions harder to understand and maintain. Help: Try reducing the number of parameters, or consider passing an object or a shape instead.

Class has too many methods. >Class has 11 methods, which exceeds the threshold of 10. Having a large number of methods can make structures harder to understand and maintain. Help: Try reducing the number of methods, or consider splitting the structure into smaller, more focused structures.

Parameter list is too long. >This list has 6 parameters, which exceeds the threshold of 5. Having a large number of parameters can make functions harder to understand and maintain. Help: Try reducing the number of parameters, or consider passing an object or a shape instead.

Parameter list is too long. >This list has 8 parameters, which exceeds the threshold of 5. Having a large number of parameters can make functions harder to understand and maintain. Help: Try reducing the number of parameters, or consider passing an object or a shape instead.

Class has too many properties. >Class has 14 properties, which exceeds the threshold of 10. Having a large number of properties can make classes harder to understand and maintain. Help: Try reducing the number of properties, or consider grouping related properties into a single object.

Class has a high kan defect score. >Class has a kan defect score of 1.71, which exceeds the threshold of 1.6. Kan defect is a heuristic used by phpmetrics to estimate defect-proneness based on control-flow statements. Help: You can also consider splitting large units of code into smaller, more focused units.

Class has high complexity. >Class has a cyclomatic complexity of 29, which exceeds the threshold of 15.

Class has a high kan defect score. >Class has a kan defect score of 4.73, which exceeds the threshold of 1.6. Kan defect is a heuristic used by phpmetrics to estimate defect-proneness based on control-flow statements. Help: You can also consider splitting large units of code into smaller, more focused units.

Class has high complexity. >Class has a cyclomatic complexity of 57, which exceeds the threshold of 15.

Process completed with exit code 1.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Assigning `mixed` type to a variable may lead to unexpected behavior. >Assigning `mixed` type here. Using `mixed` can lead to runtime errors if the variable is used in a way that assumes a specific type. Help: Consider using a more specific type to avoid potential issues.

Call to deprecated method: `OpenTelemetry\SDK\SdkBuilder::setEventLoggerProvider`. >This method is deprecated The method `OpenTelemetry\SDK\SdkBuilder::setEventLoggerProvider` is marked as deprecated and may be removed or its behavior changed in future versions. Help: Consult the documentation for `OpenTelemetry\SDK\SdkBuilder::setEventLoggerProvider` for alternatives or migration instructions.

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Use of the `isset` construct. >Ambiguous check due to `isset()` conflating existence and null comparison `isset()` returns false for both unset variables and null values. It is unclear whether you're checking for variable existence or non-null value. Help: Use explicit null comparison (`!== null`) or the null coalescing operator (`??`).

Method has a high halstead volume and effort >Method exceeds halstead volume and effort threshold(s) Halstead volume is 3022.5 (threshold 1000). Volume estimates the code's overall size/complexity. Halstead effort is 24114.28 (threshold 5000). Effort estimates the mental effort required to develop/maintain the code. Help: Consider breaking this into smaller, more focused functions.

TODO should be tagged with (@username) or (#issue). >TODO comment is untagged Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).

TODO should be tagged with (@username) or (#issue). >TODO comment is untagged Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).

TODO should be tagged with (@username) or (#issue). >TODO comment is untagged Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).

TODO should be tagged with (@username) or (#issue). >TODO comment is untagged Help: Add a user tag or issue reference to the TODO comment, e.g. TODO(@azjezz), TODO(azjezz), TODO(#123).

Loop body is empty. >This loop body is empty and performs no actions Empty loops are often a sign of a logic error or dead code. Help: Consider removing this loop or adding meaningful logic to its body.

Consider using early continue pattern to reduce nesting. >This if statement wraps the entire loop body >The loop can benefit from early continue to improve readability This pattern improves readability by reducing nesting levels. Help: Invert the condition and use `continue` to exit early, then place the main logic outside the if block.

Avoid boolean flag parameters. >This parameter acts as a boolean flag >Boolean type declared here Boolean flags often indicate a function has more than one responsibility, making it harder to understand and test. Help: Refactor by splitting the function into two separate methods, each with a clear, descriptive name.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Avoid boolean flag parameters. >This parameter acts as a boolean flag >Boolean type declared here Boolean flags often indicate a function has more than one responsibility, making it harder to understand and test. Help: Refactor by splitting the function into two separate methods, each with a clear, descriptive name.

Consider using early continue pattern to reduce nesting. >This if statement wraps the entire loop body >The loop can benefit from early continue to improve readability This pattern improves readability by reducing nesting levels. Help: Invert the condition and use `continue` to exit early, then place the main logic outside the if block.

Avoid boolean flag parameters. >This parameter acts as a boolean flag >Boolean type declared here Boolean flags often indicate a function has more than one responsibility, making it harder to understand and test. Help: Refactor by splitting the function into two separate methods, each with a clear, descriptive name.

Avoid `else` clauses. >This `else` clause can often be eliminated Code is often clearer when the main logic is not nested inside an `if` statement. Help: Consider refactoring to use an early return (a guard clause) to simplify the control flow.

Use `while` loop instead of `for` loop. >This `for` loop can be simplified to a `while` loop This `for` loop can be simplified to a `while` loop since it doesn't have initializations or increments. Help: Use a `while` loop instead of a `for` loop.