> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pikopod.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Security policy

> How to report a vulnerability in pikopod.

## Supported versions

pikopod is pre-v1. Security fixes land on the latest release only.

| Version | Supported |
| ------- | --------- |
| latest  | Yes       |
| older   | No        |

## Reporting a vulnerability

Report security vulnerabilities privately through [GitHub Security Advisories](https://github.com/pikopod/pikopod/security/advisories/new). Do not open a public issue for a security vulnerability.

Include as much as you can:

* A description of the issue and its impact.
* Steps to reproduce, or a proof of concept.
* The pikopod version (`pikopod --version`) or commit SHA.
* Your platform and Go version if you built from source.

You can expect an acknowledgement within three business days and an assessment within ten. You will be kept updated as a fix is worked on, and credited in the advisory unless you prefer to stay anonymous.

## Operational security

How pikopod behaves in a production request path, what leaves the machine, and how redaction works are documented under [Security](/operations/security).