# Security policy
## Supported versions
| `main` | Security fixes are developed here |
| Latest 0.x release | Best-effort security fixes |
| Older releases | Not supported |
RustTorch is early-stage software. A supported version is not a guarantee of a
response time, fix, or suitability for a particular threat model.
## Report a vulnerability
Use GitHub's
[private vulnerability reporting](https://github.com/newpoluton-alt/RustTorch/security/advisories/new).
Include affected versions, platform and backend, impact, reproduction steps or
proof of concept, and any suggested mitigation. Remove credentials, personal
data, and unrelated proprietary material.
Do not open a public issue, discussion, or pull request for an undisclosed
vulnerability. Do not use the Code of Conduct reporting route for security
reports. If GitHub does not offer the private form, use the repository
[Security page](https://github.com/newpoluton-alt/RustTorch/security) and wait
for private reporting to be enabled rather than publishing details.
## Handling and disclosure
The maintainer limits report access while assessing scope, dependencies,
affected releases, and a fix. Reporters may be asked to validate a patch or
coordinate a disclosure date. The project does not promise an acknowledgement
or remediation deadline. Public disclosure should wait until a fix or explicit
maintainer agreement, unless legal or safety obligations require otherwise.
Usage questions, unsupported configurations, and performance reports without a
security impact belong in the channels described by [SUPPORT.md](SUPPORT.md).