netlify/gotrue

An JWT based API for managing users and issuing JWT tokens.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 18 minutes ago
Added to GitGenius on September 15th, 2026
Created on May 16th, 2016
Open Issues & Pull Requests: 14 (+0)
GitHub issues: Enabled
Number of forks: 327
Total Stargazers: 4,483 (+0)
Total Subscribers: 52 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 41.7 days
Mean response time: 67.5 days
90th percentile: 211.0 days
Tracked items: 6

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

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

Recent activity

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

Top labels

  • stale (6)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

GoTrue is a JWT-based API for managing user registration and authentication in applications.

The tool solves the problem of handling user signup, login, and token management by providing a self-contained authentication service built on OAuth2 and JWT standards. It accepts configuration through environment variables or a .env file, with required settings for database connection, JWT signing secrets, and site URL. The service listens on a configurable port and stores user data in a MySQL database, requiring manual migration execution before first use.

GoTrue suits teams building Jamstack projects or APIs that need to offload authentication logic to a dedicated microservice rather than implementing it directly in their application. It works well for projects requiring custom user data storage and JWT-based token issuance. The tool is particularly useful when you want to run authentication as a separate, independently scalable service. It supports disabling signups to restrict user creation to invitation-only flows, rate limiting on token endpoints, and request ID inheritance for tracing purposes. For migration scenarios, it offers a user export feature protected by a configurable secret.

The project maintains active development with regular commits addressing bug fixes and feature improvements. The codebase shows consistent attention to production concerns including configurable logging levels, optional distributed tracing integration with Datadog, and support for multi-instance deployments with operator token verification. The tool demonstrates maturity in its handling of database migrations, flexible configuration management, and security-focused features like JWT audience grouping and admin role support.