Get involved
Contributing to Keeplas
Keeplas is built in the open and welcomes contributors of every experience level. Here is how to get from a fork to a merged pull request.
The workflow
Three steps to your first contribution.
- 1
Fork & clone
Fork the repo and set up your local environment with pnpm. See the Self-Hosting guide for the full bootstrap.
- 2
Make focused changes
Follow the coding standards, write tests for new functionality, and keep commits atomic.
- 3
Open a pull request
CI runs lint, typecheck and tests automatically. A maintainer reviews and merges once approved.
Before you start
A couple of housekeeping items keep the project sustainable.
- check_circleRead CONTRIBUTING.md for the workflow and code style
- check_circleSign the Contributor License Agreement (CLA)
- check_circleFollow the Code of Conduct -- be respectful and constructive
Restricted areas
Some directories are gated by CODEOWNERS and require founder approval, because they hold the cryptographic core: packages/crypto/ (AES-256-GCM, Argon2id, ML-KEM-768, Shamir) and security/. You can still propose changes there -- they just get extra review.
Reporting a vulnerability
Found a security issue? Email security@keeplas.com. Please do not open a public GitHub issue for vulnerabilities -- responsible disclosure keeps users safe.
Find a good first issue
Look for the "good first issue" label to get started.