Detect Remix in any GitHub repo

Remix is a full-stack React framework built around web standards, nested routes and loaders/actions, now merged into React Router v7.

Why show Remix on your README

Because Remix and React Router overlap, a card that reads the actual dependencies is more reliable than a badge someone typed two versions ago.

How Remix is detected

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

  • Files or folders: /^remix\.config/, remix.config.js, remix.config.ts
  • Dependencies in package.json: @remix-run/react, @remix-run/node

Remix README badge

A static badge you can paste anywhere in Markdown:

Remix badge

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

Tech stack card for remix-run/remix
remix-run/remix · 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.