SecureToolKit is a pre-1.0 open-source security library. Community support is best-effort and does not include operational, compliance, or production-safety assurances.
- Use a GitHub issue for reproducible build failures, documentation defects, or confirmed library bugs.
- Use GitHub Discussions for integration questions and design discussion when Discussions are enabled.
- Use the contribution process for proposed changes.
- Follow SECURITY.md for vulnerabilities or suspected security defects.
Before opening an issue, include the Swift version, operating system, exact SecureToolKit commit or tag, minimal reproduction steps, expected result, and actual result. Remove secrets, credentials, personal data, customer data, raw prompts, and sensitive tool arguments.
Maintainers cannot validate a Host application's authentication, trusted time, atomic Consumption, replay storage, key management, audit durability, executor, deployment, or regulatory compliance through a support issue. SecureToolKit does not make an integration production-safe by itself.
There is no guaranteed response time or commercial support commitment.
Do not publish exploit details or conduct reports in a general support issue. Use the private path described in SECURITY.md or CODE_OF_CONDUCT.md.