aarondl/authboss

The boss of http auth.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on January 3rd, 2015
Open Issues & Pull Requests: 41 (+0)
GitHub issues: Enabled
Number of forks: 223
Total Stargazers: 4,194 (+0)
Total Subscribers: 57 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 567.6 days
Mean response time: 567.6 days
90th percentile: 567.6 days
Tracked items: 1

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Authboss is a modular authentication and authorization library for Go web applications that handles user registration, login, password recovery, and session management.

The library solves the problem of building secure authentication systems from scratch by providing pre-built, composable modules for common auth workflows. It works by offering a set of pluggable handlers and middleware that integrate with your HTTP server, allowing you to enable features like two-factor authentication, OAuth2 integration, and account lockout policies without reimplementing the underlying logic. The architecture separates concerns into distinct modules so you can use only what you need rather than adopting an all-or-nothing framework.

Authboss suits developers building Go web applications who want authentication without the overhead of a full framework. It works well for projects where you need fine-grained control over user flows and session handling while avoiding the complexity of building auth from first principles. The modular design means you can start with basic login and registration, then add features like password reset or two-factor authentication incrementally as requirements evolve. It is particularly useful if you are already committed to Go's standard library patterns and want something that fits naturally into that ecosystem rather than imposing its own conventions.

The project shows consistent maintenance with regular updates addressing bugs and adding features. Pull requests receive timely review and feedback from maintainers. Issues are actively triaged and responded to, indicating engagement with user needs. The codebase demonstrates attention to security concerns, with authentication-related changes receiving careful scrutiny. Documentation is kept current alongside code changes, suggesting the maintainers prioritize usability alongside functionality.