Skip to main content

Security

ccleft follows the TunaOS security policy.

Supported versions​

Security fixes land on main. Only the latest release and main are supported.

Reporting a vulnerability​

Do not open a public issue for security vulnerabilities.

GitHub private vulnerability reporting is not currently enabled on this repository. Per the TunaOS policy, report privately by opening a draft security advisory in tuna-os/tunaOS (Security -> Advisories -> New draft security advisory). Name tuna-os/ccleft as the affected repository and include the affected component, a minimal reproduction, the impact, and a suggested fix if you have one.

Never include real credentials, tokens, or account identifiers in a report. Redact captures first.

Disclosure​

The TunaOS policy aims to acknowledge reports within 5 business days. We prefer coordinated disclosure: please allow a reasonable window for a fix before publishing details.

Scope​

ccleft reads provider credentials read-only and must never refresh, rewrite, or create credential files. Bugs that break that guarantee, leak secrets in output or metrics, or mishandle upstream payloads are in scope. Vulnerabilities in the provider services themselves should go to their own maintainers.