# Security Policy
## Supported Versions
Only the latest release is supported with security updates. If a
vulnerability affects an older version, the recommended action is to
upgrade to the latest `git-nav` release.
## Reporting a Vulnerability
Please **do not open a public issue** for security-related bugs.
Instead, report them privately via GitHub's built-in
[private security advisory flow](https://github.com/oskarizu/git-nav-rs/security/advisories/new).
That keeps the details visible only to the maintainer while a fix is
being prepared.
This is a side project maintained in spare time, so please treat any
response times as best-effort rather than a hard SLA:
- I'll aim to **acknowledge** the report within a couple of weeks.
- If accepted, a patched release will follow as time allows — no
guaranteed timeline, but critical issues (arbitrary code execution,
credential exposure) will jump the queue.
- I'll keep you updated as the investigation progresses.
If you'd prefer email, you can also reach the maintainer at
`oscar@oskarizu.net` — but the GitHub advisory flow is preferred because
it keeps the paper trail in one place and lets us request a CVE.