Stripe restricted live key
Part of Security, which counts for 30% of the overall score. When this check fires it deducts 25 points from that category, once per scan, no matter how many places it turns up.
What it detects
A Stripe restricted live key (rk_live_...) was found. It still authenticates to the live API with whatever scopes the restricted key was granted.
Why it matters
A Stripe restricted live key authenticates to the live API with whatever scopes it was granted, so a leak still exposes those operations. Restricted does not mean safe to commit. It stays in git history after removal.
How to fix it
Move the key into a server-side environment variable and read it at runtime. Roll the restricted key in the Stripe dashboard. Keep its scopes as narrow as the task requires.
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