GitHub refresh token
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 15 points from that category, once per scan, no matter how many places it turns up.
What it detects
A GitHub OAuth refresh token (ghr_...) was found. It can be exchanged for fresh access tokens, so it extends access over time.
Why it matters
A GitHub OAuth refresh token can be exchanged for fresh access tokens, so it extends account access over time rather than expiring quickly. A leaked refresh token is a durable foothold. It belongs only in encrypted server-side storage.
How to fix it
Keep refresh tokens in a server-side secret store or encrypted database column, read at runtime. Revoke the exposed authorization so the refresh token can no longer be exchanged.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo