brocoders/nestjs-boilerplate

NestJS boilerplate. Auth, TypeORM, Mongoose, Postgres, MongoDB, Mailing, I18N, Docker.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 60 minutes ago
Added to GitGenius on September 15th, 2026
Created on August 23rd, 2020
Open Issues & Pull Requests: 51 (+0)
GitHub issues: Enabled
Number of forks: 957
Total Stargazers: 4,398 (+0)
Total Subscribers: 31 (+0)

Repository Insights (GitGenius)

Median issue/PR response: N/A
Mean response time: 22.5 days
90th percentile: 26.9 days
Tracked items: 34

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 609 days
Stale 30+ days: 7
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • question (5)
  • Not a bug (2)
  • enhancement (2)
  • bug (1)
  • documentation (1)

Most active issues this week

Detailed Description

NestJS Boilerplate is a starter template for building REST APIs with NestJS that includes authentication, database integration, mailing, internationalization, and Docker support.

The boilerplate addresses the common problem of setting up a production-ready NestJS project from scratch by providing a pre-configured foundation with essential features already integrated. It includes authentication mechanisms, support for multiple databases through TypeORM and Mongoose, email functionality, internationalization for multi-language support, and Docker containerization. The template follows NestJS conventions and patterns, allowing developers to begin building application-specific logic immediately rather than spending time on infrastructure setup.

This boilerplate suits teams building REST APIs who want to avoid repeating standard setup work across projects. It works well for applications requiring user authentication, database persistence with either relational or document databases, and multi-language support. The project provides a fully compatible frontend boilerplate as part of a broader ecosystem, suggesting it is designed for full-stack teams working on coordinated backend and frontend implementations.

The project maintains active continuous integration with automated Docker end-to-end testing. Dependency updates are managed through automated tooling. The codebase includes seed data functionality and comprehensive API documentation accessible through Swagger, with a live demo environment available for reference.