2026-05-22 16:17:15 +02:00
|
|
|
# Security Policy
|
|
|
|
|
|
|
|
|
|
## Supported versions
|
|
|
|
|
|
|
|
|
|
Wickra is pre-1.0. Security fixes are applied to the latest released `0.1.x`
|
|
|
|
|
version only; please upgrade to the newest release before reporting an issue.
|
|
|
|
|
|
|
|
|
|
| Version | Supported |
|
|
|
|
|
| --- | --- |
|
|
|
|
|
| 0.1.x (latest) | :white_check_mark: |
|
|
|
|
|
| older 0.1.x | :x: |
|
|
|
|
|
|
|
|
|
|
## Reporting a vulnerability
|
|
|
|
|
|
|
|
|
|
**Do not open a public issue for a security vulnerability.**
|
|
|
|
|
|
|
|
|
|
Report it privately through one of:
|
|
|
|
|
|
2026-05-30 12:18:10 +02:00
|
|
|
- GitHub's [private vulnerability reporting](https://github.com/wickra-lib/wickra/security/advisories/new)
|
2026-05-22 16:17:15 +02:00
|
|
|
("Report a vulnerability" under the repository's *Security* tab), or
|
2026-05-31 23:22:57 +02:00
|
|
|
- email to **support@wickra.org** with a subject line starting with
|
2026-05-22 16:17:15 +02:00
|
|
|
`[wickra security]`.
|
|
|
|
|
|
|
|
|
|
Please include:
|
|
|
|
|
|
|
|
|
|
- the affected version(s) and platform / language binding,
|
|
|
|
|
- a description of the issue and its impact,
|
|
|
|
|
- steps to reproduce, ideally a minimal proof of concept.
|
|
|
|
|
|
|
|
|
|
## What to expect
|
|
|
|
|
|
|
|
|
|
- An acknowledgement within **5 working days**.
|
|
|
|
|
- An assessment and, if confirmed, a planned fix with a target release.
|
|
|
|
|
- Coordinated disclosure: we will agree on a disclosure date with you and
|
|
|
|
|
credit you in the release notes unless you prefer to stay anonymous.
|
|
|
|
|
|
|
|
|
|
## Scope
|
|
|
|
|
|
|
|
|
|
In scope: the published crates (`wickra-core`, `wickra-data`, `wickra`), the
|
|
|
|
|
PyPI/npm packages, and the build/release workflows in `.github/workflows/`.
|
|
|
|
|
|
|
|
|
|
Out of scope: vulnerabilities in third-party dependencies (report those
|
|
|
|
|
upstream; we track them via Dependabot and `cargo-deny`).
|
