---
title: "Vercel Security Review now covers repos without a project"
description: "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."
canonical_url: "https://www.outofplace.space/blog/vercel-security-review-unlinked-repos"
language: "en"
last_updated: "2026-11-16"
alternates:
  pl: "https://www.outofplace.space/pl/blog/vercel-security-review-repozytoria-bez-projektu.md"
---

# 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.

Published 2026-11-16 · Category: Vercel & AI SDK · Tags: Security, AI agents

Yes: since 13 November 2026, [Vercel Security Review reviews pushes to GitHub repositories](https://vercel.com/changelog/vercel-security-review-no-longer-requires-a-linked-vercel-project) 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](https://vercel.com/docs/agent/security-review#turn-on-security-review) 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](https://vercel.com/changelog/vercel-security-review-public-beta) 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.

  - Security Review now has two kinds of review: project reviews (a repository linked to a Vercel project) and repository reviews (any other repository in a connected GitHub account).
  - The default scope for repositories is everything the Vercel GitHub App can access; narrow it to whole accounts or single repositories, up to 1,000.
  - Leaving a project out of Projects to Review doesn't stop reviews of its repository: it then gets a repository review of the whole repository.
  - Repository reviews cost the same as project reviews, apply only the team policy and are hidden from Contributors.
  - Neither the changelog nor the docs say whether teams that turned reviews on before 13 November now cover all repositories, so check the setting.

## 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](https://www.outofplace.space/blog/dev-digest-2026-11-09#vercel-security-review-public-beta-billed-after-10-november) 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:

| Date             | What happened                                                                       | Source                                                                                                                 |
| ---------------- | ----------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- |
| 2 November 2026  | Security Review announced; reviews of repositories that don't deploy on Vercel promised "next" | [Security Review announcement](https://vercel.com/blog/vercel-security-review)                                                 |
| 3 November 2026  | Public beta for Pro and Enterprise teams, free until 10 November                     | Public beta changelog, linked above                                                                                              |
| 10 November 2026 | End of "free until"; after it, each review is billed at the Vercel Agent rate       | Public beta changelog                                         |
| 13 November 2026 | Repositories without a Vercel project can be reviewed, all of them by default       | No 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](https://vercel.com/docs/agent/security-review#projects-and-repositories):

|                         | Project review                                  | Repository review                                       |
| ----------------------- | ----------------------------------------------- | ------------------------------------------------------- |
| Needs                   | A Vercel project connected to the repository    | The repository's GitHub account connected to the team   |
| Code in scope           | The project's root directory                    | The whole repository                                    |
| Base for the diff       | The branch's previous deployment, when there is one | The branch's previous review, else the pushed commit's parent |
| Security policies       | Team and project policy                         | Team policy only                                        |
| Who sees findings       | Owner, Member, Developer, Security; Contributors for assigned projects | Owner, Member, Developer, Security    |
| GitHub check and PR comments | Yes                                        | Yes                                                     |
| Price                   | Vercel Agent rate                               | The 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](https://vercel.com/docs/git/vercel-for-github#grant-the-vercel-github-app-access-to-the-repository). 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](https://vercel.com/docs/agent/security-review/usage#roles-and-permissions). 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](https://docs.github.com/en/apps/using-github-apps/reviewing-and-modifying-installed-github-apps#modifying-repository-access) 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](https://vercel.com/docs/agent/pricing#security-review) 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](https://www.outofplace.space/blog/dev-digest-2026-11-08#vercel-security-review-scans-every-push-now-at-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](https://www.outofplace.space/blog/nextjs-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](https://www.outofplace.space/blog/dev-digest-2026-11-09#vercel-ci-no-longer-needs-a-linked-vercel-project), dated 3 November: a different feature with its own settings.
- **Still a public beta.** The [Security Review docs](https://vercel.com/docs/agent/security-review) 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](https://vercel.com/docs/agent/security-review/usage#triage-findings) 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](https://vercel.com/kb/guide/deepsec-reviews-on-vercel) 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.

## Further reading

- [Vercel Security Review no longer requires a linked Vercel project](https://vercel.com/changelog/vercel-security-review-no-longer-requires-a-linked-vercel-project): The changelog of 13 November 2026: repository reviews and the default that covers every unlinked repository.

- [Vercel docs: Security Review](https://vercel.com/docs/agent/security-review): Setup, Projects to Review and Repositories to Review, project against repository reviews, and pricing.

- [Vercel docs: Managing Security Reviews](https://vercel.com/docs/agent/security-review/usage): Triage, fixes with Vercel Agent, team and project policies, and the roles that can change each setting.

- [Vercel Agent pricing](https://vercel.com/docs/agent/pricing): The Vercel Token Rate of $0.25 per million tokens, billing consent and where to track Security Review costs.

- [Vercel Security Review is now in public beta](https://vercel.com/changelog/vercel-security-review-public-beta): The changelog of 3 November 2026: Pro and Enterprise, free until 10 November.

- [GitHub docs: Reviewing and modifying installed GitHub Apps](https://docs.github.com/en/apps/using-github-apps/reviewing-and-modifying-installed-github-apps): Where to see and change which repositories the Vercel GitHub App can access.

- [Vercel guide: deepsec reviews on Vercel](https://vercel.com/kb/guide/deepsec-reviews-on-vercel): Running the deepsec agent on a schedule against chosen GitHub repositories.

- [Vercel Schedules replace cron jobs, Security Review beta](https://www.outofplace.space/blog/dev-digest-2026-11-09): Vercel, 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.
