Korers is not yet public. The source code releases in Q3 2026.
This document explains how you can contribute now and what to expect when the code drops.
There is no code to contribute to yet. That is intentional.
What you can do right now:
- Star the repository to signal interest and join the Early Access queue
- Open an Early Access Request if you want to test before public release
- Report issues with this documentation if something is wrong or unclear
- Start a Discussion if you have questions, ideas, or want to introduce yourself
When the source code is published in Q3 2026, contributions will be welcome in these areas:
Bug reports Open an issue with a clear description, steps to reproduce, and your environment. No bug report templates yet - just be specific.
Security vulnerabilities Do not open a public issue. Read the Security Policy first.
Feature requests Open an issue and describe what you want and why. We will be honest about whether it fits the direction of the project.
Pull requests We will publish contribution guidelines alongside the source code. For now: keep changes focused, write tests for what you touch, explain what you did and why.
Code audits The core engine is written in Rust. The encryption and key derivation code will be the first thing we want eyes on. If you are a security researcher, that is where we need you most.
We are not looking for every contributor. We are looking for the right ones.
Useful backgrounds:
- Rust development
- Security research and cryptography
- React and TypeScript for the desktop UI
- React Native for the mobile app
- Enterprise IT and DevSecOps for real-world testing
Everything happens on GitHub for now.
- Issues for bug reports and feature requests
- Discussions for everything else
- No Slack, no Discord, no mailing list yet
This project follows a simple rule: be direct, be honest, be respectful.
Read the full Code of Conduct.
By contributing to Korers, you agree that your contributions will be licensed under the MIT License.