01 / Technologies / Testing

Detect Vitest in any GitHub repo

Vitest is a Vite-native test runner with a Jest-compatible API, fast watch mode and in-source testing.

Why show Vitest on your README

Test runners are always treated as dev-only, so you can show them with `categoryFilter=devtools` or hide them with `prodonly`.

How Vitest is detected

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

  • Files or folders: /^vitest\.config/
  • Dependencies in package.json: vitest

Vitest README badge

A static badge you can paste anywhere in Markdown:

Vitest badge

Markdown
![Vitest](https://img.shields.io/badge/Vitest-6E9F18?style=for-the-badge&logo=vitest&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 Vitest (and everything around it) appears or disappears on its own:

Tech stack card for vitest-dev/vitest
vitest-dev/vitest · 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.