Klyra is intended for authorized security testing in owned labs, internal environments, CTFs, and written-scope assessments.

Security fixes target the main branch until versioned releases are created.

Open a private security advisory on GitHub if available, or file an issue with non-sensitive reproduction details.

Include:

• Affected commit or version
• Impact
• Reproduction steps in a safe lab
• Expected vs actual behavior
• Suggested remediation if known

Do not include live secrets, private target data, or exploit details against third-party systems.

Klyra must not be used to attack systems without explicit authorization. Reports or contributions that add malware, credential theft, persistence, evasion, destructive behavior, or unauthorized access workflows will be rejected.