GitLab personal 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 GitLab personal access token (glpat-...) was found. It authenticates to the GitLab API with the scopes assigned to it.
Why it matters
A GitLab personal access token authenticates to the GitLab API with the scopes assigned to it, which can include reading and pushing code or running pipelines. A committed token is usable by anyone who reads the repo. It stays in history after removal.
How to fix it
Store the token in a CI/CD variable or environment variable and read it at runtime. Use the minimum scopes required. Revoke the exposed token in GitLab under access tokens.
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