Security Review
An automated code security review capability within the Vercel platform that scans code changes in GitHub repositories directly to detect vulnerabilities. It supports change-level scanning and context-enhanced analysis of projects.
Timeline (last 90 days)
Vercel's security review feature can now scan code changes for vulnerabilities without linking a GitHub repository to a Vercel project.
Previously, Vercel's security review was usually tied to linked projects and deployment workflows, and repositories not linked to a Vercel project could not use the feature.
When a push creates a deployment for a linked project with Security Review enabled, the review uses additional project and deployment context to provide richer analysis.
By default, Security Review covers all unlinked repositories that the Vercel GitHub App can access in connected GitHub accounts.
Organizations can limit Security Review's coverage to selected connected accounts or individual repositories in the Agent settings.
Security Review's toggle and coverage scope are managed centrally in the Vercel Agent settings rather than scattered across each project's deployment configuration.
Once enabled, every code push to a covered repository automatically triggers a review of the corresponding code changes, with no additional configuration or manual operation required.
Vercel states explicitly that Security Review analyzes source code; it is not a security audit, does not perform runtime testing or penetration testing, and does not guarantee that an application has no vulnerabilities.
The Vercel Security Review feature is now in public beta for Pro and Enterprise teams.
Security Review itself is currently free, a status that lasts until November 10, 2026; fixes generated using Vercel Agent are billed at Agent rates.
6 more timeline events
All Facts (16)
Once enabled, every code push to a covered repository automatically triggers a review of the corresponding code changes, with no additional configuration or manual operation required.
50%UnverifiedVercel's security review feature can now scan code changes for vulnerabilities without linking a GitHub repository to a Vercel project.
50%UnverifiedPreviously, Vercel's security review was usually tied to linked projects and deployment workflows, and repositories not linked to a Vercel project could not use the feature.
50%UnverifiedWhen a push creates a deployment for a linked project with Security Review enabled, the review uses additional project and deployment context to provide richer analysis.
50%UnverifiedBy default, Security Review covers all unlinked repositories that the Vercel GitHub App can access in connected GitHub accounts.
50%UnverifiedOrganizations can limit Security Review's coverage to selected connected accounts or individual repositories in the Agent settings.
50%UnverifiedSecurity Review's toggle and coverage scope are managed centrally in the Vercel Agent settings rather than scattered across each project's deployment configuration.
50%UnverifiedVercel states explicitly that Security Review analyzes source code; it is not a security audit, does not perform runtime testing or penetration testing, and does not guarantee that an application has no vulnerabilities.
50%UnverifiedSecurity Review itself is currently free, a status that lasts until November 10, 2026; fixes generated using Vercel Agent are billed at Agent rates.
50%UnverifiedVercel Security Review starts its review from GitHub push events, so code pushed directly to production branches and code from force pushes also enters the review scope.
50%UnverifiedAll projects affected by a single push are reviewed together rather than queued project by project.
50%UnverifiedEach finding records the project, environment, branch and commit, along with a summary, a suggested fix and an AI-generated severity rating.
50%UnverifiedSecurity Review adds a separate GitHub check for each commit it reviews; if the commit is associated with a PR, it also posts findings as review comments and links back to the finding details.
50%UnverifiedFor public repositories, the specific details of findings stay within the dashboard and are not exposed.
50%UnverifiedTeams can write security policies in natural language that apply to all projects or to specified projects; team-level policies are configured in Agent settings, and project-level policies are configured in the project's Security settings.
50%UnverifiedThe Vercel Security Review feature is now in public beta for Pro and Enterprise teams.
50%