ueberauth/guardian

Elixir Authentication

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 41 minutes ago
Added to GitGenius on September 19th, 2026
Created on June 16th, 2015
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 388
Total Stargazers: 3,514 (+0)
Total Subscribers: 48 (+0)

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

  • stale:discard (2)
  • Note:Discussion (1)
  • stale:keep (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Guardian is an authentication library for Elixir applications that uses token-based authentication with JSON Web Tokens by default.

Guardian solves the problem of implementing authentication across diverse Elixir systems by providing a flexible token-based approach. The library treats tokens as its core currency and supports JWT out of the box, but allows developers to implement custom token types by adhering to the Guardian.Token behaviour. Tokens can carry arbitrary claims and assertions, both standard and application-specific. The tool integrates with Plug and Phoenix but operates independently of them, making it usable in TCP/UDP protocols, Phoenix channels, or any system where authentication tokens can be attached.

Developers should choose Guardian if they need authentication that works across multiple contexts within a single Elixir application, including web endpoints, channels, and custom protocols. The library's support for multiple token types and configurations in one application suits projects with complex authentication requirements. Guardian's flexibility in token implementation means it can adapt to different security needs rather than forcing a single approach.

The project maintains active test coverage and inline documentation. Development activity shows consistent attention to code quality and API stability.