Repo brief: tariqbuilds/linux-dash

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T20:01:55.089Z · commit 186a802ea76e

Verdict

Mixed — Stale — last commit 2y ago

• 19 active contributors
• MIT licensed

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against dependency CVEs from deps.dev and OpenSSF Scorecard

What it is

linux-dash is a lightweight web-based system monitor for Linux that displays real-time CPU, memory, disk, and process metrics in a drag-and-drop dashboard interface. It solves the problem of requiring heavyweight monitoring tools (Nagios, Grafana) on resource-constrained systems by keeping the entire application under 400KB on disk and offering pluggable server backends (Node.js, Go, Python, PHP) so operators can choose their preferred stack. Client-server monorepo: app/index.html is the AngularJS 1.3.4 frontend, with plugins in src/js/plugins/ and core features (charts, tables, loaders) in src/js/core/features/. Server-side logic lives in app/server/ with parallel implementations…

Start here

Open these first:

• app/server/index.js — Primary Node.js entry point; initializes Express server, WebSocket connections, and routes system metric queries to the…
• src/js/core/app.js — AngularJS application bootstrap and module definition; wires together routing, services, and feature directives that…
• src/js/core/server.service.js — Client-side service that handles all HTTP and WebSocket communication with the backend server to fetch and stream system…
• app/server/linux_json_api.sh — Shell script that parses Linux /proc and system commands to extract CPU, memory, disk, network, and process metrics in…
• src/js/plugins — Directory of metric visualization plugins (CPU charts, RAM, disk, network) that register with the core app and consume data…

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

# Clone the repository
git clone --depth 1 https://github.com/afaqurk/linux-dash.git
cd linux-dash/app/server

# Install Node.js dependencies (if using Node.js backend)
npm install --production

# Start the server on port 80 (or override with LINUX_DASH_SERVER_PORT=8080)
node index.js

The dashboard will be accessible at http://localhost/ (or the configured port). For other runtimes, see Go, Python, or PHP sections in the README.

Daily commands:

Node.js (recommended): npm install --production && node index.js (listens on 0.0.0.0:80 by default; override port with LINUX_DASH_SERVER_PORT=8080 and host with LINUX_DASH_SERVER_HOST=127.0.0.1). Go: `go r…

…shortened for this brief.

Key cautions & unknowns

• Stale — last commit 2y ago
• Concentrated ownership — top contributor handles 70% of recent commits
• No CI workflows detected
• 1. Port permissions: Default port is 80, which requires sudo on Linux; use LINUX_DASH_SERVER_PORT env var or --port flag to avoid this. 2. WebSocket requirement: The dashboard relies on a persistent…
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.