Newshot
Account

Vercel Security Review no longer requires a linked Vercel project

Summary

You can now scan code changes for vulnerabilities with Vercel Security Review in GitHub repositories that have not yet been linked to a Vercel project. By default, Security Review covers all unlinked repositories the Vercel GitHub App can access in a connected GitHub account. You can limit coverage to selected connected accounts or individual repositories in Agent settings. Once enabled, each push to a covered repository automatically triggers a review of its code changes. Security Review checks commits directly in repositories with Security Review enabled, without requiring a Vercel project or deployment. When a push creates a deployment for a linked project with Security Review enabled, the review uses the additional project and deployment context. Connect the account in your team’s Git settings , then enable Security Review in Vercel Agent settings . Get started with the Security Review documentation . Read more

Original text(via Vercel Blog)
题图
题图

You can now scan code changes for vulnerabilities with Vercel Security Review in GitHub repositories that have not yet been linked to a Vercel project.

By default, Security Review covers all unlinked repositories the Vercel GitHub App can access in a connected GitHub account. You can limit coverage to selected connected accounts or individual repositories in Agent settings. Once enabled, each push to a covered repository automatically triggers a review of its code changes.

Security Review checks commits directly in repositories with Security Review enabled, without requiring a Vercel project or deployment. When a push creates a deployment for a linked project with Security Review enabled, the review uses the additional project and deployment context.

Connect the account in your team’s Git settings, then enable Security Review in Vercel Agent settings.

Get started with the Security Review documentation.

Contributors

The text above was extracted automatically from the source page and may miss images, tables or code blocks. The original is authoritative.

Published by Vercel Blog
This site only summarises and aggregates; copyright stays with the original author. Headlines and summaries follow the source — where they differ, the original wins.
Read the original ↗