Good first issues
Issues labelled for newcomers — scoped, reviewed, and ready to pick up.
Get involved
Contribute to NexaCore OS.
The source is public and Apache-2.0, the protocol specifications are public domain, and forks are first-class citizens by design. Clone it, build it, boot it — then pick up an issue, propose a change, join the conversation, or support the work directly.
Start here
Clone it, build it, boot it.
You don't need real hardware to see NexaCore OS run. On an x86-64 Linux host with a Rust toolchain, the same script CI runs will build the kernel, wrap it in a UEFI image, and boot it under QEMU.
git clone https://github.com/CySalazar/nexacore-os
cd nexacore-os
# Prerequisites: QEMU + OVMF (UEFI firmware) — Debian/Ubuntu:
sudo apt-get install -y qemu-system-x86 ovmf
# Build the kernel-runner, produce a UEFI image, boot it, assert the banner:
bash scripts/qemu-boot-smoke.shWhere to help
Good first steps.
The project is early and honest about it. Documentation review, threat-model refinement, and crypto-API sanity checks are the highest-value contributions today — but every well-scoped PR is welcome.
How we work
Sign off your commits (DCO -s), use Conventional Commits, and run cargo fmt && clippy && test before pushing.
Propose a change
Protocol changes, breaking APIs, new TEE backends, and governance changes go through the NCIP process.
By participating you agree to the Code of Conduct (Contributor Covenant v2.1).
Join the community
Where the conversation happens.
GitHub Discussions
Questions, ideas, show-and-tell, and NCIP discussion — asynchronous, searchable, and right next to the code.
Real-time chat on Matrix
An open, decentralized chat — on-brand for a privacy-first project. The room opens with the public launch; the joining link is announced in Discussions.
Support the project
Right now, the best support is your work, not your money.
NexaCore OS doesn't take donations yet. Funding opens once the project has a foundation to hold it: money received and spent under a published governance and funding policy, not before. Until then the support that moves the project is direct: review the code, sharpen the threat model, improve the docs, and file good issues.
When funding opens it will appear here, and the first line item is an external cryptographic audit of nexacore-crypto. The terms are already set by the funding policy: contributions buy no influence over the protocol or governance, and spending is reported publicly.
Found a security issue?
Please don't open a public issue. Follow the coordinated-disclosure process — encrypted reports to [email protected].
Prefer to say hello first?
Introduce yourself.
Not ready to open a PR? Tell us where you'd like to help and we'll point you at the right place. We read every message.