Detect Vercel in any GitHub repo

Vercel is a frontend cloud platform for deploying Next.js and other frameworks with previews on every pull request.

Why show Vercel on your README

A vercel.json in the repo means a deploy target; the card adds it to the infra section so readers know where the app lives.

How Vercel is detected

Stack Fingerprint reads the repo's full file tree in one GitHub API call and flags Vercel when it finds any of these:

  • Files or folders: vercel.json, .vercelignore

Vercel README badge

A static badge you can paste anywhere in Markdown:

Vercel badge

Markdown
![Vercel](https://img.shields.io/badge/Vercel-000000?style=for-the-badge&logo=vercel&logoColor=white)

Or let the repo describe itself

Static badges go stale the moment you swap a dependency. A Stack Fingerprint card is generated from the repo, so Vercel (and everything around it) appears or disappears on its own:

Tech stack card for vercel/next.js
vercel/next.js · generated live from the repo
README.md
[![Stack Fingerprint](https://stackfingerprint.vercel.app/api/card?repo=OWNER/REPO)](https://stackfingerprint.vercel.app/?repo=OWNER/REPO)

Replace OWNER/REPO with your repository, or open the builder to pick a theme and layout.

02 / Related articles