The Pulse
Vercel opens paid Security Review to unlinked GitHub repositories
Vercel Security Review can now scan changes in GitHub repositories without a linked Vercel project. The public-beta tool charges for each push reviewed and defaults to covering accessible repositories in connected accounts.

GitHub repositories no longer need a linked Vercel project to have their code changes scanned by Vercel Security Review, the company said in a changelog post. Once enabled, the tool reviews each push to a covered repository for vulnerabilities without requiring a deployment.
Security Review is part of Vercel Agent and is available in public beta on Pro and Enterprise plans. Findings appear in the team's Vulnerabilities dashboard.
Choosing repositories
By default, the service covers unlinked repositories that the Vercel GitHub App can access in a connected GitHub account. Teams can instead select whole connected accounts or individual repositories, up to 1,000 repositories, or select no repositories.
For repositories without a project, the owning GitHub account or organization must first be connected to the team through its Git settings. Each GitHub account can be connected to one Vercel team, and reviews are limited to repositories the app can access.
Teams configure project and repository coverage separately in Agent settings. Excluding a project does not by itself stop reviews of its repository if repository settings still cover it.
What each review covers
Each push to a selected project or repository starts a billed review. Pricing consists of provider inference at the underlying token rate without markup, plus the Vercel Token Rate of $0.25 per million tokens. Repository and project reviews cost the same.
For a repository review, the service compares changes against the branch's previous review, falling back to the pushed commit's parent. When there is no base, such as for a project's first review, it reads the full source. Project reviews cover a project's root directory; repository reviews cover the whole repository.
When a push creates a deployment for a linked project with Security Review enabled, the review also uses project and deployment context. A repository review uses the team's security policy, while a project review can use both team and project policies.
Findings and limits
Security Review reports findings in the dashboard and adds a GitHub check to each commit it reviews. On private or internal repositories, it also posts findings as comments when the commit's branch has an open pull request. On public repositories, it posts only the check, with finding details kept in the dashboard.
Teams can use Vercel Agent to propose a fix and open a pull request; nothing merges automatically. The company says Security Review analyzes source code but is not a security audit, does not perform runtime or penetration testing, and cannot guarantee an application is free of vulnerabilities.
Sources
Related stories
- Forever Security Finds Browser Flaws in Five AI Coding Tools
- GitHub Says New Git Storage Architecture Supported 5,000 Concurrent Agents in Internal Testing
- GitHub Octoverse: Agents Started More Than 40% of September Pull Requests
- Vercel raises Token Pass credit to $150 at the same monthly price
- Vercel adds MiniMax H3 Image models to AI Gateway