keybase/client

Keybase Go Library, Client, Service, OS X, iOS, Android, Electron

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 7th, 2026
Created on January 11th, 2015
Open Issues & Pull Requests: 4,254 (+0)
GitHub issues: Enabled
Number of forks: 1,284
Total Stargazers: 9,248 (+0)
Total Subscribers: 284 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 46.8 hours
Mean response time: 272.9 days
90th percentile: 977.9 days
Tracked items: 192

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 19% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 108
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,366 days
Stale 30+ days: 94
Stale 90+ days: 87

Recent activity

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

Top labels

  • acked (4)
  • M1.S0 (1)
  • regression (1)

Detailed Description

Keybase is a client application suite that provides end-to-end encrypted communication and cryptographic identity verification across multiple platforms.

The project addresses the challenge of secure communication and key management by building a unified platform where users can verify identities through multiple social proofs and exchange encrypted messages and files. Its approach integrates cryptographic libraries written in Go with native applications for desktop and mobile, using a service-based architecture where the core crypto logic runs as a background service that client applications communicate with through a defined protocol.

Keybase suits developers and teams seeking integrated end-to-end encryption without managing separate key infrastructure. The desktop application runs on macOS, Linux, and Windows via Electron, while mobile support covers iOS and Android through React Native. The command-line client provides programmatic access for automation. The README explicitly warns that some code in the repository represents explorations and may not function as documented, so users seeking stable installations should use official releases rather than building from source. External contributors should be aware that pull requests from forks do not trigger CI builds for security reasons; builds only run after a team member reviews and merges changes to the primary fork.

The project maintains active development across all client platforms with coordinated releases. The team uses pre-commit hooks to enforce code quality standards on all commits. Internal progress tracking occurs in Jira while GitHub serves as the public interface for issue reporting and pull requests, with both channels checked and updated regularly.