# Security Policy
## Supported Versions
Confium is pre-1.0. Only the latest release line receives security fixes.
| 0.1.x | :white_check_mark: |
| < 0.1 | :x: |
## Reporting a Vulnerability
**Do not open a public GitHub issue for security vulnerabilities.**
Please report vulnerabilities by emailing the Ribose security contact at
`open.source@ribose.com`. Include:
- A description of the issue and its potential impact
- Steps to reproduce or proof of concept
- Affected versions, if known
- Suggested mitigation or fix, if any
You should receive an acknowledgement within 5 business days. Please do not
disclose the vulnerability publicly until a fix has been released.
## Security Review Process
All reports are triaged by maintainers. We may request additional information
or coordinate a joint disclosure timeline. Credit will be given in the release
notes unless you prefer to remain anonymous.
## Supply Chain
- All dependencies are pulled from crates.io. `cargo-deny` enforces license
and advisory gates in CI.
- Releases are published from `main` by the `release-plz` GitHub Action
using the `CARGO_REGISTRY_TOKEN` secret. No manual publishes.