# Deployments can now require cryptographically-verified commits

By Steven Van · 2025-11-24

The GitHub-only setting cancels deployments for any commit GitHub hasn't cryptographically verified.

Deployments from GitHub-connected [Vercel](<https://creatorstoolbox.com/tools/vercel>) projects can now be restricted to commits that GitHub has cryptographically verified. The setting is off by default and is enabled per project under Settings, Git, Require Verified Commits.

Once enabled, Vercel only creates a deployment for commits GitHub has verified; any other commit has its deployment automatically cancelled. The feature is available for GitHub projects only.

![Vercel](<https://www.google.com/s2/favicons?domain=vercel.com&sz=128>)

Vercel

The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.

[View Vercel →](<https://creatorstoolbox.com/tools/vercel>)

[Original source](<https://vercel.com/docs/project-configuration/git-settings#verified-commits>)

[Read Deployments can now require cryptographically-verified commits on Creators Toolbox](<https://creatorstoolbox.com/blog/vercel-deployments-can-now-require-cryptographically-verified-commits>)

---
Canonical source: https://creatorstoolbox.com/blog/vercel-deployments-can-now-require-cryptographically-verified-commits