Detect NestJS in any GitHub repo

NestJS is a structured Node.js framework for server-side apps, using TypeScript decorators, modules and dependency injection.

Why show NestJS on your README

Nest implies a particular architecture (modules, providers, guards); listing it sets expectations for contributors before they open the code.

How NestJS is detected

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

  • Files or folders: nest-cli.json
  • Dependencies in package.json: @nestjs/core

NestJS README badge

A static badge you can paste anywhere in Markdown:

NestJS badge

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

Tech stack card for nestjs/nest
nestjs/nest · 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.