Contributing and security

Contributions to KitchooK! are welcome. Start with the repository’s contribution guide, search existing issues, and use the issue templates for reproducible bugs or focused feature proposals.

A pull request should remain focused, include tests for behavior changes, update user documentation and the changelog where appropriate, and pass the cookbook and website checks. Changes to workflows, dependencies, builder code, contracts, and deployment infrastructure require maintainer review. Pull-request checks use GitHub-hosted runners and cannot access owner-instance infrastructure.

Report vulnerabilities privately

Do not disclose a suspected vulnerability in an issue, pull request, or other public channel. Read the security policy, then submit the report through GitHub Private Vulnerability Reporting.

Include the affected source or builder version and digest, reproduction steps, likely impact, and a suggested mitigation when possible. The current support window and response expectations are maintained in the security policy.