Session Kit is maintained by one person alongside other work, so this policy says only what one person can actually keep.

Security fixes go into the current release. There are no dated support windows and nothing is back-ported to an older line: if you are running an older release, the fix is to move to the current one.

releases/latest resolves to the current beta. All releases lists it and everything published before it. Earlier lines stay published so that whatever you already downloaded keeps its checksum and provenance files beside it, not because those lines still receive fixes.

The current release supports its documented Linux targets and macOS 14 or newer on Apple Silicon and Intel. Other operating systems, older macOS releases, Apple Bash 3.2, and service arrangements outside the documented systemd and per-user launchd models are outside this policy.

Do not publish vulnerability details, exploit steps, terminal output, provider content, UUIDs, local paths, or credentials in an issue.

Use GitHub private vulnerability reporting from the repository Security tab:

https://github.com/dob323/session-kit/security/advisories/new

If private reporting is unavailable, open a public issue containing only a request for a private contact channel. Do not describe the vulnerability.

Include privately:

• affected tag or full commit;
• operating system, architecture, and dependency versions;
• the security boundary involved;
• minimal reproduction with secrets removed;
• whether a live session or private data can be changed or exposed;
• a safe temporary workaround, if known.

The maintainer will acknowledge a valid private report, investigate it, and coordinate disclosure after a fix is available. Response times are a best-effort beta service, not an emergency support guarantee.

Session Kit is local-only and has no telemetry. It reads local process, provider, shpool, configuration, and private Session Kit state.

It does not isolate hostile processes running as the same Unix user. Such a process may read owner-accessible terminal state or edit owner-writable files.

On macOS, Session Kit uses a per-user LaunchAgent in the logged-in GUI user's domain. It does not install a privileged system daemon and does not provide a service before that user logs into the Mac desktop. Watchdog repair is Linux-only; the macOS watchdog remains report-only.

Optional terminal journals are off by default because they may contain credentials, source code, prompts, and terminal output. Read Security and local data before enabling them.