We reproduced the status of the violations that were affected

Summary

On June 16, 2025, the service that holds the detections was updated with code that mistakenly sent an incorrect deletion message. Instead of reporting a branch deletion, the message was interpreted as a full repository deletion. Consequently, the service that holds the detections automatically resolved all violations across multiple repositories, even though these repositories were not actually deleted. The publishing of problematic messages lasted approximately 14 hours, until June...