elk-zone/elk

A nimble Mastodon web client

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 34 minutes ago
Added to GitGenius on September 11th, 2026
Created on November 14th, 2022
Open Issues & Pull Requests: 657 (+0)
GitHub issues: Enabled
Number of forks: 619
Total Stargazers: 6,034 (+0)
Total Subscribers: 59 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 days
Mean response time: 78.6 days
90th percentile: 243.1 days
Tracked items: 228

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 82% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "s: accepted" is answered fastest, typically in about 35 hours, while "c: parity" waits about 3 weeks. Only 5% of issues opened in the past year have been closed. Three people close 75% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 157
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 693 days
Stale 30+ days: 141
Stale 90+ days: 127

Recent activity

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

Top labels

  • c: bug (159)
  • c: feature (80)
  • s: pending triage (66)
  • s: accepted (57)
  • c: parity (26)
  • c: ui (22)
  • c: fediverse (16)
  • c: a11y (12)

Most active issues this week

Detailed Description

Elk is a nimble Mastodon web client built with Vue and Nuxt.

Elk addresses the need for a lightweight, responsive web interface to Mastodon by providing a client optimized for performance and usability. The tool connects to any Mastodon server instance, allowing users to interact with the fediverse through a modern web application rather than relying solely on the official Mastodon web interface or native apps.

Elk suits developers and users who want a fast, minimal Mastodon client or those running their own Mastodon instances who need an alternative web interface. The project is particularly valuable for self-hosted deployments, as it can be containerized and deployed behind reverse proxies with SSL/TLS termination. The tool maintains both a production deployment and a canary deployment that reflects the latest development changes, allowing users to test new features before they reach the stable release.

The project maintains active engagement with its community through a Discord server and tracks work via an open issue board. Development includes regular deployments to the canary environment on every commit to the main branch, indicating continuous integration practices. The team accepts contributions and actively solicits feedback from users, suggesting an open development model responsive to community input.