Vercel Security Review Now Bills Pushes to Repos Vercel Doesn't Host

Vercel Security Review can now scan GitHub repositories that have no Vercel project, and its default setting covers every repository the Vercel GitHub App can reach in a team’s connected accounts. Every push to a covered repository starts a billed review, and the beta’s free period ended Nov. 10 (Vercel changelog, Nov. 13, 2026).

What Changed

Vercel launched Security Review in public beta for Pro and Enterprise teams on Nov. 2, as part of Vercel Agent. Until this week it reviewed only repositories linked to a Vercel project. The Nov. 13 update adds repository reviews, which need only the GitHub account or organization connected in the team’s Git settings.

The Security Review docs, last updated Oct. 30, list three options under Repositories to Review: All repositories (the default), specific repositories (up to 1,000) or none. The docs warn that with All repositories, “every repository the Vercel GitHub App can access in your connected GitHub accounts” starts a billed review on each push.

Reviews trigger on pushes, not pull requests, so direct pushes and force pushes to production count too. A project review reads only the project’s root directory. A repository review reads the whole repository, using the branch’s previous review or the pushed commit’s parent as its base.

What It Costs

Security Review bills at the Vercel Agent rate: provider inference at cost with no markup, plus a Vercel Token Rate of $0.25 per million input, output and cached tokens, according to Vercel’s Agent pricing docs. The pricing table lists no included reviews, and Vercel’s Nov. 3 launch changelog said the free period ran until Nov. 10. Fixes made with “Fix with Vercel Agent” are billed separately at the same rate.

Turning the feature on also opts a team into Agent usage-based billing if it wasn’t already, and that first save needs an Owner or Billing role. Teams on a flexible commitment are billed against it instead.

Removing a project from Projects to Review does not stop reviews of its repository, according to the docs. The repository has to be left out of Repositories to Review too.

How Others Read It

Help Net Security’s Nov. 5 report described Security Review as a context-aware scanner that checks whether a changed line is reachable before it reports anything, and it drew those details from Vercel’s blog and statements by its CTO.

The Take

This is Firerun’s read, not Vercel’s. Scanning repos Vercel doesn’t host is a reasonable move. APIs, workers and infrastructure code often live in repositories that never deploy to Vercel, and they hold the same secrets and authorization logic as the frontend.

The default is the problem. GitHub’s install screen lets an organization grant an app all repositories or a selected list, and a team that granted the Vercel GitHub App everything gets the broadest scope here too. On an organization with a few hundred active repos, All repositories turns every commit, including bot commits from dependency updaters, into a metered model call. Vercel’s pricing docs say cost “scales with how often you push and how much code changed,” so the bill shows up on the Agent Usage page after the fact.

Before saving Security Review settings, check what the GitHub App can see. Pick specific repositories, or trim the App’s access in GitHub first. Teams that turned it on during the free week should open Agent Usage now.

Key Takeaways

• The default, All repositories, includes everything the Vercel GitHub App can access in connected accounts.
• Every push to a covered repo is a billed review: provider inference plus $0.25 per million tokens. The free period ended Nov. 10.