Discofork
Repository brief

nicolargo/glances

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T15:53:14.636Z
1mo ago

nicolargo/glances

Glances is a production-stable, actively maintained Python system monitoring tool for Linux, BSD, macOS, and Windows. It targets local and remote real-time monitoring with a curses UI, web UI, and API support, and it has a large upstream footprint: 32,215 stars, 1,709 forks, and a recent push on 2026-03-30. Forks may be interesting if you want to extend monitoring, exporters, container support, or integrations around a mature cross-platform codebase.

GitHub
Loading tags...
Stars32,215
Forks1,709
Default branchdevelop
Last pushed2026-03-30T11:58:44Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs
Selected

Choose this fork only if its older web/API and Grafana-specific behavior is the requirement. For most adopters, upstream Glances is the better default because this fork is very stale and likely missing a long list of newer fixes and features.

Prefer upstream unless you specifically need this fork's legacy customizations. This fork looks useful only for adopters who want an older, highly customized Glances codebase and are prepared to own maintenance; it is a poor fit for users who want current features, active fixes, or low-risk deployment.

Prefer upstream unless you specifically need the fork’s API/UI/plugin changes and are prepared to maintain a highly divergent codebase. This fork looks like a customization-oriented branch, not a safe drop-in replacement for users who want current Glances features and fixes.

Prefer upstream unless you specifically need this fork's custom web/API/dashboard behavior. This fork is materially outdated and best treated as a legacy customization branch, not a general-purpose replacement.

Prefer upstream unless you already depend on this fork’s historical UI/export customizations. For new adopters, the staleness and deep divergence outweigh the likely benefits.

Choose this fork only if you need its legacy Grafana/UI customizations and are willing to accept a very stale, highly diverged codebase. For most adopters, upstream is the better default because it is active, broader in scope, and far more current.

Prefer upstream for almost any new deployment. Choose this fork only if you need legacy Windows-client behavior or must preserve an old 2013-era Glances variant and accept major feature and maintenance gaps.

Choose upstream unless you explicitly need this exact older snapshot. This fork does not add functionality, and its main tradeoff is lagging behind current Glances fixes and improvements.

Prefer upstream Glances unless you specifically need this exact frozen revision; this fork adds nothing and is far behind current development.

Adopt upstream instead unless you specifically need a frozen snapshot. This fork adds no visible value and is materially behind current Glances maintenance.