Security fixes target the latest commit on main. There are no separately
maintained release branches yet.
Please report suspected vulnerabilities through GitHub private vulnerability reporting. If private reporting is unavailable, open an issue asking for a private contact channel, without including exploit details or sensitive information.
The repository owner must enable GitHub Private Vulnerability Reporting before public publication. This document does not enable that server-side setting or establish that any public repository has been configured.
Include the affected revision, operating system, shell, terminal emulator, and steps to reproduce. Avoid sharing real directory names or private filesystem contents when a minimal example will do.
Run make audit to check dependency integrity and known reachable vulnerabilities.
CI also runs this check on pull requests, pushes to main, and a weekly schedule.
The scanner and its transitive dependencies are pinned separately in tools/.
An audit cannot establish that software is free of vulnerabilities; a failed
network request is not a clean audit. See verification.