Skip to content

Add security policy (SECURITY.md) #372

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eliaspr merged 1 commit into from
Apr 12, 2026
Merged

Add security policy (SECURITY.md) #372

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
# Security Policy

## Supported Versions

The used version scheme is `YYYY.N.P` consisting of the year of the major release, a consecutive major release number (`N`, starting at 1) and a consecutive patch number (`P`, starting at 0). At any time, only the *most recent* major release will receive security-relevant patches or bug fixes. This is shown in the following example:

```
| 2025.1.0 released with new features
| 2025.1.1 released with a bug fix
| 2025.2.0 released with new features
|
| * A vulnerability is discovered in 2025.1.x and 2025.2.x *
|
| 2025.2.1 released with security fix -> NO fix for 2025.1.x
```

## Reporting a Vulnerability

**Do not report security vulnerabilities using GitHub issues!**

If you found a security vulnerability, please contact `security@turnierplan.net`.
Loading