Thank you for your interest in BinaryFetch.
BinaryFetch is an open-source project developed under the BinaryFetch-CLI organization, with a strong focus on architectural clarity, stability, and long-term maintainability.
Please read this document carefully before contributing.
BinaryFetch follows a maintainer-driven, phase-based development model.
This means:
- The source code is open and publicly available.
- Development priorities are defined by the core maintainers.
- Contributions are accepted only if they align with the current development focus.
This approach prevents architectural drift and ensures consistent, intentional growth.
BinaryFetch targets Windows only. The Windows version has been released and its core architecture is considered stable.
- Bug fixes
- Stability improvements
- Minor refinements
- Regression fixes
- Documentation updates
- Issues and discussions aligned with the roadmap
- Large refactors
- Major architectural changes
- Feature expansions outside the roadmap
- Platform expansions (Linux, macOS, etc.)
- Random module additions
Well-written code may still be declined if it is out of scope.
Pull requests must be linked to an approved issue.
- Review the current roadmap and open issues
- Pick an existing issue or open a new issue describing your proposal
- Wait for maintainer approval before starting work
Unlinked or unsolicited PRs may be closed without review.
- Target the appropriate branch as specified by maintainers
- Keep PRs focused and minimal
- Follow the existing coding style
- Avoid unrelated changes in the same PR
- Write clear and descriptive commit messages
Maintainers reserve the right to request changes or decline PRs.
Forking BinaryFetch is allowed under the project license.
However:
- The project name must not be misrepresented
- Original authorship and license information must remain intact
- Forks must not claim to be the original BinaryFetch project