Only the latest release is supported with security fixes.
| Version | Supported |
|---|---|
| 0.1.x | ✅ |
Do not open a public issue for security vulnerabilities.
Report privately via GitHub's built-in mechanism: Report a vulnerability
Include:
- A description of the vulnerability and its impact
- Steps to reproduce
- Any suggested fix or mitigation
You will receive a response within 7 days. If the issue is confirmed, a fix will be released as soon as practical and credited to you in the changelog unless you prefer to remain anonymous.
lkf is a build-system framework that runs as the invoking user. It does not
run as root except where explicitly requested (e.g. sudo calls in
lkf toolchain install-deps). The primary security concerns are:
- Patch authenticity —
lkf patch fetchdownloads patches from upstream repositories over HTTPS. Uselkf build --verify-gpgto verify kernel tarballs against kernel.org GPG signatures. - Arbitrary code execution —
remix.tomlfiles are parsed and their fields passed to shell commands. Do not useremix.tomlfiles from untrusted sources. - Credential exposure —
GITHUB_TOKENis used only for GitHub API rate limiting inpatches/fetch.sh. It is never logged or written to disk.