How do you catch vulnerabilities on direct pushes to production?
Direct and force pushes to production branches bypass PR-based security checks, leaving real coverage gaps. Vercel Security Review, now in public beta for Pro and Enterprise teams, runs automatically on every push to a connected GitHub repository and reports findings in the Vulnerabilities dashboard.
What it is
Security Review is an automated source code vulnerability scanner that triggers on push events rather than pull requests, so direct and force pushes to production branches are reviewed too. Each finding records the project, environment, branch, and commit, with a summary, a suggested fix, and an AI-generated severity rating.
- Adds a GitHub check to each reviewed commit
- Posts findings as PR review comments linking back to each finding
- Every project affected by a single push is reviewed together
Applied case
A team member force pushes directly to the production branch, bypassing the usual PR review flow. Security Review still triggers on that push event, analyzes the affected projects, and surfaces a finding with severity rating and suggested fix in the dashboard. The developer clicks Fix with Vercel Agent, which proposes a fix and opens a PR that merges only after approval. Alternatively they run vercel security vulnerabilities in the Vercel CLI to let their own coding agent handle it.
- Fix with Vercel Agent opens a PR; nothing merges until you approve it
- No agent? Copy any finding as Markdown or JSON to feed your own tools
Read more
Recommended for you
- VerificationSuperpowersClaude Code
How do you stop agents from inventing tests that prove nothing?
An agent writes code, then writes a test for it. The test passes right away and proves nothing. Fix: no production code without a failing test first.
- VerificationSuperpowersClaude Code
Why is your agent's first fix attempt usually wrong?
An agent hits a bug, guesses a fix, reports done. The bug returns because the fix treated a symptom. Fix: no fixes without root cause.
- Verification
How do you debug a silent CMS webhook without guessing?
My CMS said "Published just now" and my site never changed. Claude found three separate causes by reading logs and data state instead of screenshots.
- VerificationSuperpowersClaude Code
Why does your AI agent say done when the work isn't?
The most expensive AI bug is not bad code. It is the agent claiming the work is done, and you trusting the claim without checking.
Enjoyed this article?
Subscribe for new articles. No spam. Unsubscribe anytime.