mum4k/termdash

Terminal based dashboard.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 10 minutes ago
Type:Library / SDKCategory(s):Terminal, Shell & TUIDeveloper Tools
Added to GitGenius on September 22nd, 2026
Created on March 24th, 2018
Open Issues & Pull Requests: 49 (+0)
GitHub issues: Enabled
Number of forks: 149
Total Stargazers: 3,038 (+0)
Total Subscribers: 27 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.4 days
Mean response time: 1158.8 days
90th percentile: 2315.2 days
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,550 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

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

Top labels

  • question (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Termdash is a cross-platform customizable terminal-based dashboard library written in Go.

The tool addresses the need to build interactive dashboards within terminal environments. It provides a framework for creating layouts with widgets, handling user input through keyboard and mouse events, and rendering content with support for colors, borders, margins, and padding. The architecture emphasizes code readability, maintainability, and testability as core design goals, representing a rewrite of earlier terminal UI concepts with improved engineering practices.

Termdash suits developers building monitoring tools, system administration interfaces, or any application requiring a terminal-based visual dashboard. The library includes widgets for buttons, text input, gauges, pie charts, and donuts, along with layout systems using binary trees or grids. It handles terminal window resizing dynamically and supports both periodic and event-driven screen redraws. The project acknowledges that breaking changes may occur until version 1.0.0, with all such changes documented in the changelog.

Development activity shows consistent engagement with the codebase. The project maintains clear separation between public and private APIs, with private packages marked by a /private/ directory in their import paths. Documentation is comprehensive, including design goals, requirements, and high-level design documentation alongside a wiki covering the public API surface. The presence of multiple demonstration files for individual widgets indicates active maintenance of examples and user-facing resources.