Timing-unsafe token comparison
Comparing secrets with === is vulnerable to timing attacks: the comparison short-circuits on the first mismatched byte, leaking information about how many bytes were correct. Token and HMAC comparisons must use a constant-time function like crypto.timingSafeEqual.
HOW VIBECHECK DETECTS THIS
vibecheck clones your repository and runs Gitleaks, Semgrep, njsscan, and a suite of custom checks targeting patterns common in AI-generated code. This check is part of the Auth & Sessions category. When a matching pattern is found, Claude triages the finding and produces a plain-English explanation and a concrete fix — no security expertise required.
FREE SCAN
Check your repo for this and 50+ other issues
Connect GitHub → vibecheck scans for secrets, unauthenticated routes, RLS gaps, injection, and more. Claude explains every finding. Free for 2 repos.
scan my repo for free →