Skip to content
kirchDevPublic

About

No description, website, or topics provided.

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

24 Commits

Folders and files

Repository files navigation

Security Policy

This is the default policy for every repository in the kirchDev organization that does not ship a SECURITY.md of its own. A repository's own policy takes precedence.

Reporting a Vulnerability

Please do not file a public GitHub issue for security problems.

Use one of the following private channels:

  1. GitHub Private Vulnerability Reporting (preferred, where enabled): open the repository's Security tab and choose Report a vulnerability.
  2. Email: titus.kirch@kirch.dev.

Please include:

  • The affected repository, and the file, version or commit.
  • A description of the vulnerability and its impact.
  • Steps to reproduce.
  • Any suggested fix, if you have one.

Never put credentials or personal data into a report.

What to expect

Stage Target timeline
Acknowledgement of report within 3 business days
Initial assessment & triage within 7 business days
Fix released (if accepted) depends on severity — critical issues prioritised
Public disclosure & advisory coordinated with reporter after the fix ships

Maintained by Titus Kirch / IT-Dienstleistungen Titus Kirch.

About

No description, website, or topics provided.

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors