ProtonMail/WebClients

Monorepo hosting the proton web clients

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 12th, 2026
Created on June 8th, 2016
Open Issues & Pull Requests: 156 (+0)
GitHub issues: Enabled
Number of forks: 711
Total Stargazers: 5,586 (+1)
Total Subscribers: 167 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.6 days
Mean response time: 151.5 days
90th percentile: 435.9 days
Tracked items: 66

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 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 91
New in 7 days: 4
Closed in 7 days: 0
Avg open age: 434 days
Stale 30+ days: 82
Stale 90+ days: 67

Recent activity

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

Top labels

  • enhancement (1)
  • invalid (1)

Detailed Description

Proton Web Clients is a monorepo hosting the web applications for Proton Mail, Calendar, Drive, Account, VPN, Pass, Wallet, Lumo, and Meet.

The project solves the challenge of managing multiple interconnected web applications that share common dependencies and modules while maintaining separate entry points and deployment targets. It uses Yarn Workspaces with unified versioning across all packages, allowing shared code in libraries like @proton/components and @proton/shared to be consumed by multiple applications. This structure enables teams to develop and release distinct web clients while reusing infrastructure and UI components.

Developers should adopt this approach if they are building a suite of related web applications that benefit from shared tooling and component libraries. The monorepo structure suits organizations maintaining multiple TypeScript and React-based web clients that need coordinated development and release cycles. The project demonstrates how to handle complex scenarios such as the VPN application, which serves different entry points across separate domains without sharing local session state, showing that the monorepo can accommodate applications with distinct deployment and authentication requirements.

The project maintains active development with regular updates to its applications and shared libraries. Work spans across multiple applications simultaneously, indicating ongoing feature development and maintenance across the entire suite. The codebase includes comprehensive tooling for development workflows, suggesting investment in developer experience and build infrastructure. Translation community involvement is actively encouraged, pointing to internationalization as an ongoing concern for the project.