Will It Vibe?npm access token
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
An npm access token (npm_...) was found. With publish rights it can push malicious versions of your packages to the registry.
Why it matters
An npm access token with publish rights can push new versions of your packages to the registry, which is a supply-chain attack on everyone who installs them. A leaked token is scanned for and abused quickly. It also grants access to private packages.
How to fix it
Move the token into a CI secret or environment variable, and prefer granular or CI-scoped tokens with short lifetimes. Read it at runtime. Revoke the exposed token in your npm account settings.
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