imbhargav5/nextbase-nextjs-supabase-starter
Grade a repo

82

/ 100

GradeB

Good shape overall. A few tweaks would push it into the top tier.

Top 28% of 5,156 graded repos

🚀⚡️ Free Boilerplate and Starter kit for Next.js 16+, Supabase, Tailwind CSS 4 and TypeScript. 🚀 Next.js 🔥 Supabase 💻 TypeScript 💚 ESLint 🎨 Prettier 🐶 Husky 🧹 Lint-Staged 🧪 Jest 🧪 Testing Library 🕹️ Playwright ✍️ VSCode 🌪️ Vercel 🎨 PostCSS 🍃 Tailwind CSS ⚛️ React Query

Documentation74
Engineering85
Health89
TypeScript797MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

12 to address
  1. 1
    README12pt

    Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.

  2. 2
    README12pt

    Add CI/build status badges from shields.io or your CI provider to signal project health.

  3. 3
    Install and run instructions9pt

    Add a .env.example listing all required environment variables so contributors know what to set up.

  4. 4
    Reproducibility6pt

    Add .github/dependabot.yml with at least one package-ecosystem entry so dependencies are updated automatically.

Working through the fixes? Let every push regrade itself.

The free GitHub App rescans this repo on every push and posts the grade as a commit check, so the score climbs without coming back to rescan by hand.

Install the GitHub App

Scorecard

Every check, grouped by category and sorted worst-first

Documentation

74

Contributing guide5pt25

Contributing guidance is in the README, not a dedicated CONTRIBUTING.md (−20 pts).

→ Moving it to a CONTRIBUTING.md makes it easier to find and keeps the README focused. A dedicated file earns +47 pts base.

README12pt70

README is present.

Install and run instructions9pt90

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

85

Issue and PR templates6pt0

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.

Reproducibility6pt80

Lockfile present (pnpm-lock.yaml). Installs are reproducible.

Tests18pt100

Test files detected (apps/database/supabase/tests).

CI/CD14pt100

CI is configured (.github/workflows/ci.yml).

Linting and formatting5pt100

Linter or formatter configured (.editorconfig).

Project health

89

Dependency manifest6pt65

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Housekeeping3pt100

.gitignore present.

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • 59 / 72
    Commits (30d / 90d)
  • 200
    Forks
  • 8
    Releaseslatest 2y ago

Community

  • 42% - Weak
    Community health
  • -
    authors own >50% of commits
  • 797
    Watchers

Responsiveness

  • 2h
    Median issue response
  • 9h
    Median PR merge time
  • 37
    Open issues
Repository files27 root entries
  • .agents
  • .changeset
  • .github
    Good: CI is configured (.github/workflows/ci.yml).
  • .vscode
  • apps
    Good: Test files detected (apps/database/supabase/tests).
  • docs
  • packages
  • scripts
  • .editorconfig
    Good: Linter or formatter configured (.editorconfig).
  • .env.development.local.example
  • .env.local.example
  • .gitignore
    Good: .gitignore present.
  • .mergify.yml
  • .node-version
    Good: Environment pinned via .node-version.
  • .nvmrc
  • AGENTS.md
  • CHANGELOG.md
  • LICENSE
    Good: Licensed under MIT.
  • oxlint.json
  • package.json
    Good: Dependency manifest found (package.json).
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Issue: No screenshots or images in the README (−20 pts).Fix: Add a GIF, screenshot, or logo image. It is the fastest way to show what your project does.
    Good: README has code examples.
    Good: README links to a live demo or deployed app.
    Issue: No status badges in the README (−10 pts).Fix: Add CI/build status badges from shields.io or your CI provider to signal project health.
    Good: README documents how to install the project.
    Good: README documents how to run the project.
  • setup.sh
  • TROUBLESHOOTING.md
  • tsconfig.json
  • turbo.json
RepoGrade badge preview

Add this badge to your README

It updates automatically each time the repo is re-graded.

[![RepoGrade](https://www.repo-grade.com/api/badge/imbhargav5/nextbase-nextjs-supabase-starter)](https://www.repo-grade.com/report/imbhargav5/nextbase-nextjs-supabase-starter)

More graded TypeScript repos