Security
Supported Versions
TunaOS images are built daily with weekly ISO publications. Images are
published with per-flavor tags (e.g. gnome, kde, gnome-hwe).
Only the most recent build of each flavor is actively supported.
See VERSIONING.md for the full tagging scheme.
| Variant | Base OS | Status |
|---|---|---|
| Yellowfin | AlmaLinux Kitten 10 | ✅ Mature |
| Albacore | AlmaLinux 10 | ✅ Mature |
| Skipjack | CentOS Stream 10 | ⚠️ Beta |
| Bonito | Fedora 44 | ⚠️ Beta |
| Bonito Rawhide | Fedora Rawhide | ⚠️ Beta |
| Sailfin | openSUSE Tumbleweed (rolling) | ⚠️ Beta |
| Guppy | Gentoo Linux (source-based) | ⚠️ Beta |
| Grouper | Ubuntu 26.04 | ⚠️ Beta |
| Marlin | Arch Linux (rolling) | ⚠️ Beta |
| Flounder | Debian 13 Trixie | ⚠️ Beta |
| Flounder Sid | Debian Sid (unstable, rolling) | ⚠️ Beta |
| Hummingbird | Fedora Hummingbird (hardened rolling Rawhide) | 🧪 Experimental |
| Gurnard | Ubuntu 24.04 Noble | 🧪 Experimental |
| Wahoo | Fedora ELN (EL11 preview, rolling) | 🧪 Experimental, dispatch-only |
| Redfin | Red Hat Enterprise Linux 10 | 🔒 Local-build only |
Mature means general availability. Beta means the image is available for
tests. VARIANT-LIFECYCLE.md defines both terms.
Experimental is the label that ROADMAP.md, the canonical status
table, gives to variants that are not yet Beta. Experimental variants and
variants on a moving base have best-effort availability. We do not publish
Redfin because you must build it locally.
Reporting a Vulnerability
Please do not report security vulnerabilities through public GitHub issues.
Instead, report them privately via GitHub Security Advisories:
- Go to the Security tab
- Click Report a vulnerability
- Provide a detailed description of the issue, including steps to reproduce
You can expect:
- Acknowledgment within 48 hours
- Status update within 5 business days
- Resolution timeline based on severity
Security Model
TunaOS images are:
- Built in CI from pinned base images (see
image-versions.yaml) - Signed keylessly with Sigstore Cosign using the protected TunaOS GitHub Actions workflow identity
- Scanned for vulnerabilities via GitHub's built-in scanning
- Published with signed SPDX SBOM attestations
There is no long-lived TunaOS signing key or password to leak or rotate.
Fulcio issues a short-lived certificate for the GitHub Actions OIDC identity,
and the signature is recorded in Sigstore's transparency infrastructure. See
docs/VERIFY-ARTIFACTS.md for verification commands.
Supply Chain Security
- Base images pinned by digest in
image-versions.yaml - Third-party GitHub Actions pinned to commit SHAs
- Release promotion needs successful keyless signature and SBOM-attestation verification against the expected repository workflow and protected ref
- Build secrets use BuildKit secret mounts, never environment variables
- Workflow credentials must not be embedded in URLs; use header-based Git
authentication (for example,
http.extraheader) when a private checkout is required - RPM packages from official AlmaLinux/CentOS/Fedora repositories and verified COPRs
Disclosure Policy
We follow coordinated disclosure:
- Reporter submits vulnerability privately
- We investigate and develop a fix
- Fix is deployed to new builds
- Advisory is published after deployment
See docs/AGENT_GUIDE.md for full build architecture details.