check-correctness

Static analysis detects logical errors and boundary conditions in code modules by reviewing error paths, native edge handling, and arithmetic defects. It identifies off-by-one errors, integer overflows, and concurrency problems, then classifies them by severity.

Static analysis identifies logical errors including off-by-one errors, signed and unsigned mismatches, integer overflows, state machine errors, protocol errors, and concurrency or interleaving problems. It also reviews error-path correctness, covering recovery, diagnostics, and cleanup paths.

No, this code review tool does not check for memory safety or untrusted input handling. It explicitly ignores pure style, naming, module boundaries, dependency direction, duplication, and spec conformance to focus solely on logical errors and arithmetic defects.

Run static analysis for error path and boundary condition checks when validating a module shard after development and before integration. This ensures code correctness by verifying recovery paths, error diagnostics, cleanup paths, and native function dispatch handling.

Yes, you can use this static analysis for concurrency and state machine error detection. It specifically targets interleaving problems, protocol errors, and state machine errors, alongside arithmetic defects like integer overflows and signed or unsigned mismatches.

Detected code defects are classified by severity levels of high, medium, and low during the static analysis process. This severity assessment helps reviewers prioritize logical errors, boundary conditions, and arithmetic defects found across the inspected code modules.