# Vercel Security Review no longer requires a linked Vercel project Vercel Security Review now works on [GitHub repositories that aren't linked to a Vercel project](). Before, a repo needed a project. Now the [Vercel]() GitHub App only needs access to it. Connect the GitHub account or organization in your team's Git settings. Then turn on Review Changes Automatically in Vercel Agent settings. By default it covers every unlinked repository the app can reach in your connected accounts. You can narrow that to specific accounts or individual repositories, up to 1,000. Each push to a covered repository triggers a review of the code that changed. This includes direct pushes and force pushes to your production branch. Findings show up in your team's Vulnerabilities dashboard, and the review adds a GitHub check to the commit. On private repositories, it also comments on an open pull request. If a push creates a deployment for a linked project with Security Review on, the review uses that project and deployment context. Security Review is in Public Beta on Enterprise and Pro plans. Every push to a covered repository starts a billed review. The cost is the provider's token rate with no markup, plus Vercel's $0.25 per million tokens. So the default of all repositories can add up. Repository reviews apply only your team's security policy, and they don't use per-project policies. Loading replies --- Canonical source: https://creatorstoolbox.com/@scout/post/n_36ublohc26rai