GitHub stars, forks and contributors refresh from the public API on every page load. Download figures are configured only when they have been verified.
Mission
Mouzi exists so that ordinary computer users can keep their file system organized without giving a cloud service visibility into everything they download. It is free software in both senses, MIT licensed and priced at zero, developed in public.
Numbers
762
GitHub stars
source: GitHub API
35
Forks
source: GitHub API
11
Contributors
source: GitHub API
3.5K+
Verified downloads
Across GitHub, SourceForge and independent software directories.
Source checked: August 2026
10
Languages
source: locale files in repo
2
Platforms
source: Windows, Linux
Community reach
Mouzi has attracted attention beyond GitHub through community discussions, independent coverage and word of mouth.
REDDIT
Mouzi: Organize Downloads folder automatically
r/software
130+ upvotes
Source checked: August 2026
46k views
Source checked: August 2026
A public launch thread where users discussed local-first Downloads automation and compared Mouzi with cloud organizers.
These are only a few of the public mentions. Many more threads, shares and write-ups have helped people find Mouzi, and more keep appearing. Thank you to everyone who posted, linked, mirrored or talked about the project.
Community demand
Feature direction comes from public GitHub issues: folder pickers, history filtering, recursive watching and more are all user requests tracked in the issue tracker. Translations into 10 languages were contributed by the community.
Security relevance
Downloads folders are a common delivery point for scams and malware, including fake-invoice remote-access payloads. Mouzi's rule-based sorting helps users notice files that do not belong, and the project maintains a verifiable release pipeline documented in the security docs.
Operating costs and funding
Current recurring costs are modest: domain, build minutes and testing hardware. The dominant cost is maintainer time, currently unpaid, spent on development, issue triage, documentation and release engineering.
Additional funding would directly enable:
sustained code signing and release verification infrastructure
dedicated testing across more Linux distributions and desktop environments
professional documentation and localization review
macOS support, currently experimental
more maintainer hours on community-requested features