adrianlopezroche/fdupes

FDUPES is a program for identifying or deleting duplicate files residing within specified directories.

View on GitHub ↗Jump to charts ↓

adrianlopezroche/fdupes has 3k+ stars and 200+ forks on GitHub, is written in C, and was last pushed on Apr 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 23rd, 2026
Created on May 15th, 2014
Open Issues & Pull Requests: 95 (+0)
GitHub issues: Enabled
Number of forks: 221
Total Stargazers: 3,028 (+0)
Total Subscribers: 53 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 38.7 days
Mean response time: 289.5 days
90th percentile: 1344.9 days
Tracked items: 19

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 20
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,450 days
Stale 30+ days: 20
Stale 90+ days: 19

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

fdupes is a command-line utility for identifying and removing duplicate files across specified directories.

The tool solves the problem of locating redundant files that consume disk space unnecessarily. It works by scanning directories and comparing files to detect duplicates, then offering the ability to delete them. This approach helps users reclaim storage and maintain cleaner file systems without manually searching for redundant copies.

The tool suits users who need to clean up storage across one or more directories and want a straightforward command-line interface for the task. It is particularly useful for those managing large collections of files where duplicates may have accumulated over time. The README provides minimal detail on how fdupes compares to alternative deduplication approaches, so potential users should evaluate it based on their specific workflow requirements and whether a command-line tool fits their needs.

Development activity on the project is sparse, with infrequent commits and minimal recent engagement. The repository shows limited responsiveness to issues and pull requests, suggesting the project receives only occasional maintenance attention.