Will It Vibe?GitHub OAuth access 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 access token (gho_...) was found. It carries the scopes the user granted the OAuth app.
Why it matters
A GitHub OAuth access token carries whatever scopes the user granted the OAuth app, so a leak can read or act on their repositories and account. It is a live credential until revoked. Tokens like this belong in server-side storage, never in the repo.
How to fix it
Store OAuth tokens server-side in a secret store or encrypted session, not in tracked files. Read them at runtime. Revoke the exposed token through the OAuth app or the user authorizations page.
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