DESKTOP · SERVER · EDGE · AI WORKSTATION
Security, privacy and supply-chain transparency
Developer previews are not security-certified. A hash checks file integrity, not independent signing, trustworthy builds or a warranty.
- No mandatory KINGAI cloud account or automatically downloaded model weights.
- A hash is not a replacement for signatures, SBOM, upstream license review or vulnerability response.
- Previews do not claim automatic rollback, ARM64 support or GPU certification.
- Commercial readiness requires boot, install, recovery, security and real-hardware evidence.
How to report a vulnerability
Keep exploit details, personal data and tokens out of public issues. Use the repository's private Report a vulnerability flow on GitHub. If that option is unavailable, email [email protected] with the subject Security: KINGAI-OS-Releases and include the affected release plus reproduction steps, with sensitive material sanitized.
Scope covers only material in the current release record; older copies and third-party reuploads are out of scope. There is no fixed response-time promise and no bounty program.
GitHub security page → See the verification steps before downloading →
