Vercel Security Review now covers repos without a project

Since 13 Nov 2026 Vercel Security Review reviews GitHub repos without a Vercel project, by default all the GitHub App can reach. Set the scope before you pay.

Reading time: 8 min readPublished:

Yes: since 13 November 2026, Vercel Security Review reviews pushes to GitHub repositories (opens in a new tab) that have no Vercel project. It is a product change, not a security fix: there is no CVE, no package and no version to upgrade. What matters for a team is the default. Once Security Review is on, the Repositories to Review setting starts at All repositories, which the Security Review docs (opens in a new tab) define as "every repository the Vercel GitHub App can access in your connected GitHub accounts". Every push to one of them is a billed review at the Vercel Agent rate, and the public beta changelog (opens in a new tab) made reviews free only until 10 November 2026. So today, open Agent settings, pick the repositories you want reviewed, and check what the Vercel GitHub App can reach on GitHub. We read every source on 16 November 2026; we did not run a review ourselves.

What changed in Vercel Security Review

Security Review is the part of Vercel Agent that reads the code changed in each push to GitHub and reports likely vulnerabilities, such as injection or a missing authorisation check, in the team's Vulnerabilities dashboard. Until 13 November it reviewed only repositories connected to a Vercel project, as in the Security Review public beta we covered in our digest. The changelog entry of 13 November 2026 drops that requirement: "By default, Security Review covers all unlinked repositories the Vercel GitHub App can access in a connected GitHub account."

There is no package or release behind it, so the timeline has dates instead of versions:

DateWhat happenedSource
2 November 2026Security Review announced; reviews of repositories that don't deploy on Vercel promised "next"Security Review announcement (opens in a new tab)
3 November 2026Public beta for Pro and Enterprise teams, free until 10 NovemberPublic beta changelog, linked above
10 November 2026End of "free until"; after it, each review is billed at the Vercel Agent ratePublic beta changelog
13 November 2026Repositories without a Vercel project can be reviewed, all of them by defaultNo linked project changelog

The settings now have two lists. The docs name the two kinds of review: a project review covers a repository connected to one of the team's Vercel projects, and a repository review covers any other repository in a GitHub account connected to the team. Each push is reviewed once. A push to a repository whose project is in Projects to Review gets a project review; any other push gets a repository review if Repositories to Review covers it. The two differ in ways a team will notice, per the docs on projects and repositories (opens in a new tab):

Project reviewRepository review
NeedsA Vercel project connected to the repositoryThe repository's GitHub account connected to the team
Code in scopeThe project's root directoryThe whole repository
Base for the diffThe branch's previous deployment, when there is oneThe branch's previous review, else the pushed commit's parent
Security policiesTeam and project policyTeam policy only
Who sees findingsOwner, Member, Developer, Security; Contributors for assigned projectsOwner, Member, Developer, Security
GitHub check and PR commentsYesYes
PriceVercel Agent rateThe same

For a monorepo that is the biggest difference: a project review stays inside the project's root directory, while a repository review takes in every package in the repository. When a push to a linked project also creates a deployment, the changelog says the review uses the project and deployment context too.

Who is affected and how to tell

You are affected if your team has Security Review on, or turns it on, and has connected a GitHub account in which the Vercel GitHub App can see more repositories than you deploy on Vercel. These are the setups to look at:

  • A GitHub App installed with access to all repositories. When you install the Vercel GitHub App, GitHub asks whether it may access all repositories or only selected ones, per Vercel's GitHub docs (opens in a new tab). With all repositories, the default scope of Security Review is every repository in that account, including the ones you never meant to deploy.
  • Projects you left out on purpose. The docs are explicit: "Leaving a project out of Projects to Review doesn't stop reviews of its repository." With Repositories to Review on All repositories, that repository gets a repository review instead, of the whole repository and with the team policy only. To stop it, leave it out of both lists.
  • Teams that enabled reviews before 13 November. The changelog and the docs give the default for the new setting but say nothing about teams that already had reviews on. Don't assume either way: open the setting and look.
  • Teams with Contributors. A Contributor sees findings only for assigned projects and never from repository reviews, per the Security Review roles and permissions (opens in a new tab). Findings in an unlinked repository reach Owners, Members, Developers and the Security role, and, as pull request comments on a private repository, anyone with access to that repository.

To tell where you stand, three places answer it. The team's Git settings list the GitHub accounts connected to the team; each GitHub account can be connected to one Vercel team only. The team's Agent settings, under Security Reviews, show Projects to Review and Repositories to Review. And on GitHub, the Vercel app's page under Installed GitHub Apps shows its Repository access, as GitHub's docs (opens in a new tab) describe.

How to limit Vercel Security Review to the repositories you choose

Only a team Owner can turn reviews on and change the two lists, per the roles table.

  1. List the connected GitHub accounts

    Open the team's Git settings and note every GitHub account and organisation connected under GitHub. Only these accounts can produce repository reviews.

  2. Check what the Vercel GitHub App can reach

    For each account, open Installed GitHub Apps on GitHub (an organisation's Settings, Third-party Access, GitHub Apps), click Configure next to Vercel and read Repository access. If it says All repositories and you want fewer, switch to Only select repositories and pick them. Only organisation owners can change this for an organisation.

  3. Set Repositories to Review

    In the team's Agent settings, under Security Reviews, choose Specific repositories and select whole accounts or single repositories (up to 1,000), or No repositories to keep reviews to Vercel projects only. You can't save No projects and No repositories together; to stop everything, turn off Review Changes Automatically.

  4. Set Projects to Review with the repository list in mind

    Choose All projects, Specific projects (up to 100) or No projects. A project you leave out is still reviewed as a repository if its repository is in Repositories to Review, so exclude it there too if you want no reviews of it.

  5. Write a team policy

    Repository reviews read only the team policy, so put the rules that matter for unlinked repositories there: what the code is, which folders hold sensitive logic, what not to report. The Policy field appears in the Security Reviews section once reviews are on.

  6. Read the usage after a few days of pushes

    Open Agent, then Usage, pick a time range and look at Security Review costs. If a few repositories cost most, narrow the list or move them to a project review, which stays inside the project's root directory.

What it costs

Every push to a covered repository starts a billed review. The Vercel Agent pricing page (opens in a new tab) sets the rate: provider inference at the underlying token rate with no markup, plus the Vercel Token Rate of $0.25 per million tokens, counted on input, output and cached tokens. Reviews run per push, not per pull request, so the bill grows with how often you push and how much code changes. Repository reviews and project reviews cost the same. Our advice from when Security Review moved to the Agent rate still holds: start with one busy project or repository and read the first bill.

Vercel publishes no per-review figure, and the pages we read don't name the model or a typical token count, so we give no estimate either. What we can say is where the cost moves. A repository review covers the whole repository rather than one project's root directory; the docs don't say whether that changes the token count, so in a monorepo compare the costs in Usage before you leave it on repository reviews. Fixes made with Vercel Agent from a finding are separate work, billed at the same rate. If the team isn't on Vercel Agent usage-based billing yet, the pricing page says enabling Security Review consents to it, and that first save needs an Owner or Billing member; teams on a flexible commitment are billed against the commitment.

What to watch out for

  • It is not a vulnerability patch. Nothing here fixes a bug in Vercel or Next.js. If you came for those, the Next.js 16.4.5 security release is the patch to install.
  • Not the same as Vercel CI without a project. Our digest covered Vercel CI without a linked Vercel project, dated 3 November: a different feature with its own settings.
  • Still a public beta. The Security Review docs (opens in a new tab) label it "Public Beta on Enterprise and Pro plans" as of 16 November 2026.
  • Part of the roadmap is still open. The Security Review announcement of 2 November promised reviews of deployments from the Vercel CLI and v0 as well as of repositories that don't deploy on Vercel. The 13 November changelog delivers the last part for GitHub and says nothing about CLI or v0 deployments, and neither page names GitLab or Bitbucket.
  • Public repositories show no findings on GitHub. On a public repository Security Review posts only its check, linking to the dashboard, so an unpatched issue isn't disclosed. On a private repository with an open pull request, findings become comments anyone with access to the repository can read.
  • A model's severity. The docs on triage (opens in a new tab) call severity "AI-generated estimates rather than scores against a fixed rubric", and a finding marked closed only means a later review no longer saw it. It is not an audit or a penetration test.
  • deepsec is another tool. Vercel's deepsec guide (opens in a new tab) runs the deepsec agent as a scheduled job against the repositories you list, posting to GitHub issues and Slack, with model costs through AI Gateway. It doesn't mention Security Review. Choose deepsec for scheduled reviews under your own control; Security Review for a review of every push with findings in the dashboard.

We read the changelog, the Security Review docs, the pricing page and GitHub's docs on 16 November 2026. Security Review is a beta and changes often, so check the docs before you rely on a default.

Can Vercel Security Review scan a GitHub repository without a Vercel project?

Yes, since 13 November 2026. Connect the GitHub account or organisation that owns the repository in your team's Git settings, then turn on Review Changes Automatically in Agent settings. Every push to a covered repository starts a repository review of the code that changed. GitHub is the only Git provider the changelog and docs name.

Which repositories does Vercel Security Review cover by default?

Under Repositories to Review the default is All repositories: every repository the Vercel GitHub App can access in the GitHub accounts connected to your team, on top of all projects under Projects to Review. Choose Specific repositories (whole accounts or single repositories, up to 1,000) or No repositories to narrow it.

Is Vercel Security Review free?

No. Reviews were free until 10 November 2026; since then each push to a covered repository is a billed review at the Vercel Agent rate: the model provider's token price with no markup plus $0.25 per million tokens. Repository reviews cost the same as project reviews.

Which Vercel plans include Security Review?

Pro and Enterprise, as a public beta, per Vercel's docs on 16 November 2026. Enabling it puts a team on Vercel Agent usage-based billing if it wasn't already, which a team Owner or Billing member has to accept.

What is deepsec and how is it different from Security Review?

deepsec is an AI security agent for source code that a Vercel guide runs as a scheduled job against the repositories you list, paying for models through AI Gateway. Security Review is the managed Vercel Agent feature: it reviews each push, posts a GitHub check and keeps findings in the Vulnerabilities dashboard.

Further reading

Vercel Security Review no longer requires a linked Vercel project (opens in a new tab)The changelog of 13 November 2026: repository reviews and the default that covers every unlinked repository.vercel.com
Vercel docs: Security Review (opens in a new tab)Setup, Projects to Review and Repositories to Review, project against repository reviews, and pricing.vercel.com
Vercel docs: Managing Security Reviews (opens in a new tab)Triage, fixes with Vercel Agent, team and project policies, and the roles that can change each setting.vercel.com
Vercel Agent pricing (opens in a new tab)The Vercel Token Rate of $0.25 per million tokens, billing consent and where to track Security Review costs.vercel.com
Vercel Security Review is now in public beta (opens in a new tab)The changelog of 3 November 2026: Pro and Enterprise, free until 10 November.vercel.com
GitHub docs: Reviewing and modifying installed GitHub Apps (opens in a new tab)Where to see and change which repositories the Vercel GitHub App can access.docs.github.com
Vercel guide: deepsec reviews on Vercel (opens in a new tab)Running the deepsec agent on a schedule against chosen GitHub repositories.vercel.com
Vercel & AI SDKVercel Schedules replace cron jobs, Security Review betaVercel, 2 to 9 Nov 2026: Schedules replace Vercel cron jobs, Security Review is billed after 10 Nov, workflow 5.4.0 adds idempotent starts, Claude marks text.

Tell us what we’re building.

We reply within one business day.