Detect Tailwind CSS in any GitHub repo Tailwind CSS is a utility-first CSS framework where you style elements with small composable classes directly in your markup.
Why show Tailwind CSS on your README Tailwind is one of the most-requested README badges; detecting it from the config file or dependency means it never goes stale when you upgrade to v4.
How Tailwind CSS is detected Stack Fingerprint reads the repo's full file tree in one GitHub API call and flags Tailwind CSS when it finds any of these:
Files or folders: /^tailwind\.config/Dependencies in package.json: tailwindcssTailwind CSS README badge A static badge you can paste anywhere in Markdown:
Markdown Copy
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 Tailwind CSS (and everything around it) appears or disappears on its own:
shadcn-ui/ui · generated live from the repoREADME.md Copy
[](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
Oct 13, 2026 · 3 min read
Three ways to show what your project is built with: hand-made shields.io badges, a live auto-detected stack card, or a card committed by a GitHub Action. Pros, cons and copy-paste snippets.