#mavka-findings

Mavka findings on Java order-processing code that treats a lock timeout as a duplicate delivery.

Java concurrency bugs Mavka caught in checkout code, where lock acquisition failures are reported as unavailable stock.

Mavka findings on Java locking in booking systems, where a failed tryLock is mistaken for a table that is already taken.

Bugs Mavka caught in Java loops that never terminate, including a sensor-data parser that spins forever on invalid input.

What happens when Java code assumes a string parses to a number — crashes Mavka found in rating, pricing and scoring logic.