- There was a bug in the query
go/incorrect-integer-conversionwhich meant that upper bound checks using a strict inequality (<) and comparing againstmath.MaxIntormath.MaxUintwere not considered correctly, which led to false positives. This has now been fixed.