# Vercel Security Review now in public beta

DevFeed: [Vercel Security Review now in public beta](<https://devfeed.tech/articles/vercel-security-review-now-in-public-beta-115629.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-security-review-public-beta>)

Author: Ben Sabic

Published: 2026-11-03T20:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [code security](<https://devfeed.tech/topics/code-security.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [ai code review](<https://devfeed.tech/topics/ai-code-review.md>), [Vercel](<https://devfeed.tech/topics/vercel.md>), [human-in-the-loop UX](<https://devfeed.tech/topics/human-in-the-loop-ux.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [beta](<https://devfeed.tech/tags/beta.md>), [branch](<https://devfeed.tech/tags/branch.md>), [code](<https://devfeed.tech/tags/code.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [environment](<https://devfeed.tech/tags/environment.md>), [events](<https://devfeed.tech/tags/events.md>), [free](<https://devfeed.tech/tags/free.md>), [github](<https://devfeed.tech/tags/github.md>), [github-repository](<https://devfeed.tech/tags/github-repository.md>), [helps](<https://devfeed.tech/tags/helps.md>), [inference](<https://devfeed.tech/tags/inference.md>), [public-beta](<https://devfeed.tech/tags/public-beta.md>), [report](<https://devfeed.tech/tags/report.md>), [review](<https://devfeed.tech/tags/review.md>), [security](<https://devfeed.tech/tags/security.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

## AI overview

Vercel Security Review, in public beta for Pro and Enterprise teams, automatically analyzes source code on every push to a connected GitHub repository, including direct and force pushes to production; projects affected by one push are reviewed together. Findings identify the project, environment, branch, and commit, and include a summary, suggested fix, and AI-generated severity rating. Each reviewed commit gets a GitHub check; pull requests also receive comments linking to findings, while details for public repositories remain in the dashboard. Vercel Agent can propose a fix and open a pull request for approval, or findings can be exported as Markdown or JSON or accessed with `vercel security vulnerabilities` (CLI 65.10.0 or later). Teams can add plain-language security policies. The tool analyzes source code but does not perform runtime or penetration testing and cannot guarantee an application is vulnerability-free. Pricing is provider inference at underlying token rates without markup, plus $0.25 per million tokens; reviews are free until November 10, 2026, and costs otherwise scale with push frequency and code changes.

## Source excerpt

Vercel Security Review is now in public beta for Pro and Enterprise teams. Once enabled, every push to a connected GitHub repository is automatically reviewed for vulnerabilities, and findings are reported in the Vulnerabilities dashboard. What triggers a review Security Review runs automatically when code is pushed to a connected GitHub repository. Because reviews start from push events rather than pull requests, direct and force pushes to your production branch are reviewed as well. Every project affected by a single push is reviewed together. What a finding includes Each finding records the project, environment, branch, and commit, with a summary, a suggested fix, and an AI-generated severity rating. Security Review adds its own GitHub check to each commit it reviews. When there's a pull request, it also posts findings as review comments that link back to each finding. On public repositories, finding details stay in the dashboard. Fixes and resolution Clicking Fix with Vercel Agent on a vulnerability report hands the finding to Vercel Agent, which proposes a fix and opens a pull request for you to review. Nothing merges until you approve it. To fix findings with your coding agent instead, use vercel security vulnerabilities in the Vercel CLI, or copy any finding as Markdown or JSON. Security policies Teams can write security policies in plain language, for all projects or specific ones, to give Security Review more context about how they build. Set a team policy in Agent settings and a project policy in the project's Security settings. Limitations Security Review analyzes source code. It isn't a security audit, and it doesn't perform runtime or penetration testing. It helps you find vulnerabilities but doesn't guarantee your application is free of them. Pricing Security Review is billed at the Vercel Agent rate: provider inference at the underlying token rate with no markup, plus the Vercel Token Rate of $0.25 per million tokens (input, cached, output). Reviews r