Community, Security, and Licensing

Participate

Report ordinary bugs and propose improvements through the GitHub issue tracker. Include reproduction steps, expected and actual behavior, runtime/environment information, and sanitized logs.

Use project discussions for design questions and proposals. Respect the repository's Code of Conduct.

Report vulnerabilities privately

Do not publish exploitable details in a public issue or pull request. Use GitHub private vulnerability reporting or email security@synentra.io.

Include affected version, impact, reproduction steps, and supporting evidence. Follow SECURITY.md for the current response process. This documentation does not replace that policy or create a separate response-time commitment.

Governance and conduct

Maintainer responsibilities and project decisions follow GOVERNANCE.md and the repository maintainer list. Conduct concerns can be reported to conduct@synentra.io.

Licensing and branding

Synentra source is licensed under Apache-2.0. Observe dependency notices and attribution requirements. Contributions must comply with the Developer Certificate of Origin.

The source license does not grant permission to imply official endorsement through the Synentra name or logo. Consult TRADEMARKS.md for brand usage.

When publishing modified documentation, make its version and relationship to the official project clear.