Skip to content

Update SECURITY.md for clarity on support and reporting #33

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
jkowalleck merged 2 commits into from
Jul 17, 2026
Merged

Update SECURITY.md for clarity on support and reporting #33

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
60e3e17
Update SECURITY.md for clarity on support and reporting
jkowalleck Jul 17, 2026
f51dbdb
Apply suggestions from code review
jkowalleck Jul 17, 2026
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
35 changes: 35 additions & 0 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
# Security Policy

## Supported Versions

Only the latest published version of this project is supported with security updates.

Older versions are not supported. If a vulnerability affects an older version, please first verify whether it is still present in the latest version.

## Reporting a Vulnerability

If you discover a security vulnerability, please report it through **GitHub Security Advisories** using private vulnerability reporting.

- Go to the repository’s **Security** tab.
- Choose **Report a vulnerability**.
- Submit the details privately through GitHub’s advisory workflow.
- <https://github.com/jkowalleck/rfc3987-syntax2/security/advisories/new>


Comment thread
jkowalleck marked this conversation as resolved.
Please **do not** open public issues for security vulnerabilities.

## What to Include in a Report

To help us triage and fix issues quickly, please include:

- A clear description of the vulnerability
- Steps to reproduce
- A proof of concept (if available)
- Impact assessment
- Suggested remediation (if known)

## Response Process

We will review reports and assess impact/severity.

If the report is accepted, a fix will be developed and released in the latest supported version, and a coordinated disclosure will be made through GitHub Security Advisories.