First off, thank you for considering contributing to Project Luis! It's people like you that make Luis a better tool for everyone.
- Check the existing issues to see if it's already been reported.
- If not, open a new issue using the Bug Report template.
- Open a new issue using the Feature Request template.
- Explain the "Why" and "How" of your proposal.
- Fork the repository.
- Clone it locally:
git clone https://github.com/your-username/project-Luis.git - Branch: Create a feature branch:
git checkout -b feature/amazing-feature - Build: Run
npm installand ensure tests pass. - Commit: Keep your commits clean and descriptive.
- Push:
git push origin feature/amazing-feature - PR: Open a Pull Request to the
mainbranch.
Project Luis requires:
- Node.js v18+
- SQLite (local storage)
npm install
node server.jsWe believe in shared governance and rewarding sustained contribution. Our pipeline for moving from a newcomer to a core decision-maker is transparent:
- Requirement: Your first merged Pull Request.
- Goal: Familiarize yourself with the "14 Layers of Defense" and the Polymorphic AST Challenge engine.
- Requirement: 5+ high-quality PRs merged OR providing helpful, technical reviews on 10+ PRs.
- Responsibility: You are invited to review incoming community PRs. Your approval is a strong signal for maintainers.
- Requirement: Consistent contribution over 3+ months and deep expertise in a specific module (e.g., Cryptographic Challenges or IP-Lock logic).
- Responsibility: You have write access to the repository and lead architectural decisions.
Please note that every Pull Request is audited by Project Luis's automated "Surgical Verification" pipeline. If our automated Guardian leaves a failing check on your PR, don't worry! It is designed to act as an automated mentor. Read its comments, fix the identified vulnerabilities, and push again.
Join our Discussions to talk about the future of structural security!
Directed by Anson (@ansonsaju)