01 / Technologies / Auth

Detect NextAuth in any GitHub repo

NextAuth is one of the auth technologies Stack Fingerprint recognises automatically when it scans a public repository.

How NextAuth is detected

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

  • Files or folders: /^auth\.(ts|js|tsx|jsx)$/, /\[\.\.\.nextauth\]/, /route\.(ts|js)$/, /auth/
  • Dependencies in package.json: next-auth, @auth/core

NextAuth README badge

A static badge you can paste anywhere in Markdown:

NextAuth badge

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

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.