Discofork
Repository brief

qarmin/czkawka

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-30T20:05:25.208Z
1mo ago

qarmin/czkawka

Czkawka is a mature Rust desktop/CLI utility for finding and cleaning up duplicate files, empty folders, similar images/videos, broken files, and other unwanted data. The repo is active, large, and clearly product-focused, with multiple frontends and recent bugfix/releases.

GitHub
Loading tags...
Stars30,285
Forks1,014
Default branchmaster
Last pushed2026-03-27T19:39:46Z
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 you explicitly need a legacy Czkawka snapshot with a few packaging/UI fixes. For most adopters, upstream is the better choice because this fork is far behind and missing major newer functionality.

Choose this fork only if you specifically want an unmodified upstream snapshot. For most users, upstream is the better choice because it is more current and includes recent fixes and features.

Choose upstream unless you specifically need this fork namespace; it adds no visible capabilities and is already behind current upstream fixes.

Prefer upstream unless you specifically need this older snapshot. This fork adds no visible functionality of its own and is materially behind current upstream maintenance and fixes.

Prefer upstream unless you need this exact older snapshot. This fork adds nothing new, is 39 commits behind, and looks stale, so it is only attractive as a starting point for your own downstream work or for preserving an old baseline.

Adopt this only if you specifically need the older snapshot. For normal use, upstream is the better choice because this fork adds nothing and is materially behind on fixes and improvements.

Adopt this fork only if you need a personal holding copy; otherwise upstream is the better choice because this fork adds nothing and is materially behind.

Prefer upstream unless you specifically want a frozen copy; this fork adds no visible capabilities and is materially behind current upstream.

Prefer upstream unless you specifically need this older frozen baseline; this fork adds nothing visible on its own and is mainly behind on fixes and polish.

Prefer upstream unless you specifically need this exact frozen snapshot. This fork adds no evident features, is 79 commits behind, and looks stale rather than maintained.