bubka/2fauth

A Web app to manage your Two-Factor Authentication (2FA) accounts and generate their security codes

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 14 minutes ago
Added to GitGenius on September 16th, 2026
Created on May 15th, 2019
Open Issues & Pull Requests: 20 (+0)
GitHub issues: Enabled
Number of forks: 301
Total Stargazers: 4,157 (+0)
Total Subscribers: 25 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 34.7 hours
Mean response time: 12.8 days
90th percentile: 27.1 days
Tracked items: 168

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 7% of issues opened in the past year have never received a reply. 85% of issues opened in the past year have been closed, leaving a working backlog. Three people close 82% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 2
Closed in 7 days: 2
Avg open age: 437 days
Stale 30+ days: 10
Stale 90+ days: 8

Recent activity

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

Top labels

  • bug (46)
  • fixed (42)
  • enhancement (23)
  • setup (19)
  • triage (19)
  • feature (17)
  • webextension (15)
  • docker (13)

Detailed Description

2fauth is a self-hosted web application for managing two-factor authentication accounts and generating their security codes.

The tool addresses the problem of centralizing 2FA credential management without relying on proprietary authenticator apps or cloud services. It stores 2FA account details locally and generates time-based and HMAC-based one-time passwords on demand. Users can add accounts by scanning QR codes or entering secrets manually, and the application handles the cryptographic operations needed to produce valid security codes for each configured account.

The project suits organizations and individuals who want to self-host their 2FA infrastructure and maintain full control over authentication credentials. It works well for users uncomfortable storing secrets in third-party authenticator applications or those needing a centralized dashboard to manage multiple 2FA accounts. The self-hosted nature means deployment requires running a web server, making it most appropriate for users with basic server administration capability rather than those seeking a zero-setup solution.

Development activity shows consistent engagement with the codebase. The project receives regular commits addressing bugs and adding features. Pull requests are reviewed and merged at a steady pace, indicating active maintenance. Issues are tracked and responded to by maintainers, though resolution timelines vary. The documentation is maintained alongside code changes, suggesting the team prioritizes keeping guidance current with implementation.