mirror of
https://github.com/yusufipk/OpenFrame.git
synced 2026-09-11 17:46:06 +00:00
33 lines
946 B
Markdown
33 lines
946 B
Markdown
# Security Policy
|
|
|
|
## Supported Versions
|
|
|
|
OpenFrame is under active development.
|
|
Security fixes are prioritized for the latest code on `master` and recent release tags (if available).
|
|
|
|
## Reporting a Vulnerability
|
|
|
|
Please do not report security vulnerabilities in public issues.
|
|
|
|
**Preferred:** use [GitHub private vulnerability reporting](https://github.com/yusufipk/OpenFrame/security/advisories/new) on this repository.
|
|
|
|
**Alternative:** email info@open-frame.net if you cannot use GitHub.
|
|
|
|
Include as much detail as possible:
|
|
|
|
- Affected area (API route, auth flow, upload flow, etc.)
|
|
- Reproduction steps
|
|
- Proof of concept (if available)
|
|
- Potential impact
|
|
- Suggested remediation (optional)
|
|
|
|
## What to Expect
|
|
|
|
After a private report is submitted:
|
|
|
|
1. Maintainers acknowledge receipt.
|
|
2. Impact and exploitability are triaged.
|
|
3. A fix is prepared and validated.
|
|
4. Disclosure timing is coordinated.
|
|
5. Credits are given when appropriate.
|