jwt/ruby-jwt

A ruby implementation of the RFC 7519 OAuth JSON Web Token (JWT) standard.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 7 minutes ago
Added to GitGenius on September 18th, 2026
Created on February 23rd, 2011
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 377
Total Stargazers: 3,686 (+0)
Total Subscribers: 42 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.5 days
Mean response time: 163.8 days
90th percentile: 694.9 days
Tracked items: 45

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 712 days
Stale 30+ days: 3
Stale 90+ days: 1

Recent activity

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

Top labels

  • discussion (6)
  • enhancement (6)
  • feature (6)
  • documentation (5)
  • bug (2)
  • security (2)
  • up for grabs (2)
  • help wanted (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

ruby-jwt is a Ruby implementation of the RFC 7519 OAuth JSON Web Token standard.

The tool addresses the need to create and verify JSON Web Tokens in Ruby applications. It handles token encoding and decoding with cryptographic signing and verification, protecting against algorithm substitution attacks by requiring developers to explicitly specify the algorithm during decoding rather than trusting the token header.

The gem natively supports HMAC, RSA, ECDSA, and RSASSA-PSS algorithms through the OpenSSL library, with EdDSA available through a separate extension gem. It suits any Ruby project requiring token-based authentication or secure token exchange. The tool can be extended with custom algorithm implementations by creating objects that implement the JWT::JWA::SigningAlgorithm module with the required signing or verification methods. The README emphasizes that hard-coding the algorithm during decode operations is strongly recommended to prevent vulnerability to algorithm-switching attacks.

The project maintains an active community discussion channel and provides detailed upgrade guidance between major versions. Development activity shows consistent attention to security practices and standards compliance, with documentation that prioritizes safe cryptographic usage patterns over convenience.