Good shape overall. A few tweaks would push it into the top tier.
NestJS Bun project template, Boilerplate. Auth, Better-Auth, Prisma, MongoDB, Pino, Docker.
Documentation
79
No CONTRIBUTING.md found (−47 pts base + up to −53 pts more for content).
→ Add a CONTRIBUTING.md telling newcomers how to get involved. Include setup, code style, test, and PR instructions.
README is present.
README documents how to install the project.
Licensed under MIT.
Engineering
68
No issue or PR templates found (−100 pts).
→ Add .github/ISSUE_TEMPLATE/ with bug_report.md and feature_request.md to guide contributors. It dramatically improves issue quality.
CI is configured (.github/workflows/deploy-swagger.yml).
Lockfile present (bun.lock). Installs are reproducible.
Test files detected (src/app.module.test.ts).
Linter or formatter configured (biome.json).
Project health
89
Dependency manifest found (package.json).
Repository has a description.
Actively maintained (pushed within the last month).
.gitignore present.
Repository health signals
Activity, community, and responsiveness at scan time
Activity
- —Commits (30d / 90d)
- 19Forks
- 0Releases
Community
- —Community health
- —authors own >50% of commits
- 189Watchers
Responsiveness
- <1hMedian issue response
- 1hMedian PR merge time
- 0Open issues
Repository files28 root entries
- .claude
- .githubGood: CI is configured (.github/workflows/deploy-swagger.yml).
- .husky
- .vscode
- docs
- openapi
- prisma
- srcGood: Test files detected (src/app.module.test.ts).
- .dockerignore
- .env.example
- .gitignoreGood: .gitignore present.
- .swcrc
- biome.jsonGood: Linter or formatter configured (biome.json).
- bun.lockGood: Lockfile present (bun.lock). Installs are reproducible.
- bunfig.toml
- COMMIT_CONVENTION.md
- commitlint.config.cjs
- docker-compose.dev.yml
- docker-compose.yml
- DockerfileGood: Environment pinned via Dockerfile.
- i18n
- LICENSEGood: Licensed under MIT.
- nest-cli.json
- package.jsonGood: Dependency manifest found (package.json).
- README.mdGood: README is present.Good: README is well structured with multiple sections.Good: README includes screenshots or visuals. Great for first impressions.Issue: README has no code examples (−15 pts).Fix: Show a quick-start snippet so contributors can see what using your project looks like.Good: README links to a live demo or deployed app.Good: README includes status badges.Good: README documents how to install the project.Good: README documents how to run the project.
- renovate.json
- tsconfig.build.json
- tsconfig.json