Today, each release of the KeyOS source code is published as a single commit rather than as individually merged pull requests. This allows us to protect competitive details about future product features and improvements from competitors, but as a side effect, it also makes changes harder for third parties to review and makes public contributions more difficult.
We plan to move to a model that matches a more standard, auditable commit history with change descriptions for each pull request, and a public contribution process with author attribution and GitHub-based collaboration. Sensitive work will remain private only while necessary, then be published as reviewable changes at release. Our goal is to improve transparency and security review while preserving future feature confidentiality.