auth0/nextjs-auth0
Grade a repo

84

/ 100

GradeB

Good community traction and solid fundamentals. Nearly in the top tier.

Top 24% of 5,156 graded repos

Next.js SDK for signing in with Auth0

Documentation92
Engineering76
Health94
TypeScript2,304MIT1mo ago

Top fixes

Highest-impact changes first, ranked by point weight

9 to address
  1. 1
    Tests18pt

    Set scripts.test in package.json to your actual test command, e.g. "vitest" or "jest".

  2. 2
    Contributing guide5pt

    Add setup instructions, code style notes, and how to run tests.

  3. 3
    Contributing guide5pt

    Show new contributors how to get a local dev environment running.

  4. 4
    Contributing guide5pt

    Describe your linting/formatting rules and how to run them.

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

92

Contributing guide5pt47

CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.

→ Add setup instructions, code style notes, and how to run tests.

README12pt100

README is present.

Install and run instructions9pt100

README documents how to install the project.

License6pt100

Licensed under MIT.

Engineering

76

Tests18pt35

Test files detected (e2e/app-router.spec.ts).

CI/CD14pt100

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

Linting and formatting5pt100

Linter or formatter configured (e2e/test-app/.eslintrc.json).

Reproducibility6pt100

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

Issue and PR templates6pt100

Issue or PR templates present.

Project health

94

Housekeeping3pt60

.gitignore present.

Dependency manifest6pt100

Dependency manifest found (package.json).

Repository metadata5pt100

Repository has a description.

Activity5pt100

Actively maintained (pushed within the last month).

Repository health signals

Activity, community, and responsiveness at scan time

Activity

  • -
    Commits (30d / 90d)
  • 463
    Forks
  • 113
    Releaseslatest 5y ago

Community

  • 87% - Good
    Community health
  • -
    authors own >50% of commits
  • 2,304
    Watchers

Responsiveness

  • 3d 20h
    Median issue response
  • 3d 17h
    Median PR merge time
  • 11
    Open issues
Repository files35 root entries
  • .github
    Good: CI is configured (.github/workflows/test.yml).
    Good: Dependabot covers 2 ecosystems (npm, github-actions). Dependencies stay current.
    Good: Issue or PR templates present.
  • docs
  • e2e
    Good: Test files detected (e2e/app-router.spec.ts).
    Good: Linter or formatter configured (e2e/test-app/.eslintrc.json).
  • examples
    Good: Environment pinned via examples/with-dpop/Dockerfile.
  • src
  • tests
  • .DS_Store
    Issue: Build artifacts or local files may be committed (.DS_Store) (−40 pts).Fix: Remove them and add to .gitignore.
  • .gitignore
    Good: .gitignore present.
  • .shiprc
  • .version
  • AGENTS.md
  • CHANGELOG.md
  • CODE-OF-CONDUCT.md
  • CONTRIBUTING.md
    Issue: CONTRIBUTING guide is very brief (−12 pts for depth). 150+ words earns +6 pts; 400+ earns +12 pts.Fix: Add setup instructions, code style notes, and how to run tests.
    Issue: Contributing guide lacks a setup section (−12 pts).Fix: Show new contributors how to get a local dev environment running.
    Issue: Contributing guide lacks a code style section (−8 pts).Fix: Describe your linting/formatting rules and how to run them.
    Issue: Contributing guide lacks a testing section (−8 pts).Fix: Show contributors how to run the test suite (e.g. npm test, pytest, cargo test).
    Issue: Contributing guide lacks a PR workflow section (−8 pts).Fix: Explain how to fork, branch, and open a pull request so contributors know what to expect.
    Issue: Contributing guide has no code examples (−5 pts).Fix: Add code blocks showing example commands for setup, running tests, and submitting a PR.
  • eslint.config.mjs
  • EXAMPLES.md
  • lefthook.yml
  • LICENSE
    Good: Licensed under MIT.
  • NOTICE
  • package.json
    Good: Dependency manifest found (package.json).
  • playwright.config.ts
  • pnpm-lock.yaml
    Good: Lockfile present (pnpm-lock.yaml). Installs are reproducible.
  • pnpm-workspace.yaml
  • prettier.config.mjs
  • README.md
    Good: README is present.
    Good: README is well structured with multiple sections.
    Good: README includes screenshots or visuals. Great for first impressions.
    Good: README has code examples.
    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.
  • SECURITY.md
    Good: Security policy present.
  • tsconfig.base.json
  • tsconfig.json
  • tsconfig.test.json
  • typedoc.json
  • V1_MIGRATION_GUIDE.md
  • V2_MIGRATION_GUIDE.md
  • V3_MIGRATION_GUIDE.md
  • V4_MIGRATION_GUIDE.md
  • vitest.config.mts
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/auth0/nextjs-auth0)](https://www.repo-grade.com/report/auth0/nextjs-auth0)

More graded TypeScript repos