workos/authkit

The world's best login box powered by WorkOS and Radix.

View on GitHub ↗Jump to charts ↓Open shareable report →

workos/authkit has 3k+ stars and 150+ forks on GitHub, is written in TypeScript, and was last pushed on Sep 10, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 20th, 2026
Created on October 31st, 2023
Open Issues & Pull Requests: 25 (+0)
GitHub issues: Enabled
Number of forks: 170
Total Stargazers: 3,353 (+0)
Total Subscribers: 32 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 27.9 hours
Mean response time: 38.8 days
90th percentile: 96.2 days
Tracked items: 15

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 438 days
Stale 30+ days: 18
Stale 90+ days: 17

Recent activity

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

Top labels

  • enhancement (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

AuthKit is a login component library that provides a pre-built authentication interface powered by WorkOS and Radix UI.

The tool solves the problem of building secure, user-friendly login experiences from scratch. Rather than implementing authentication UI manually, developers integrate AuthKit's ready-made login box that handles the presentation layer while delegating authentication logic to WorkOS. This approach lets teams focus on their application rather than reinventing authentication interfaces.

AuthKit suits projects that want a polished, standards-compliant login experience without the overhead of designing and maintaining custom authentication UI. It works best for teams already using or willing to adopt WorkOS as their authentication backend, since the component is tightly integrated with that service. The tool supports passwordless authentication, OAuth2, magic code flows, and single sign-on, making it suitable for applications with diverse authentication requirements.

Development on the project shows consistent activity with regular commits and pull requests being merged. The maintainers respond to issues and incorporate community feedback into updates. The codebase receives ongoing refinement and feature additions rather than remaining static.