mirror of
https://github.com/Kaelio/ktx.git
synced 2026-06-07 07:55:13 +02:00
* chore(community): rewards program, issue templates, and triage workflow Adds the public-facing community engagement infrastructure. CONTRIBUTING.md introduces a three-tier rewards program (sticker / t-shirt / hoodie) gated on merged PRs, with explicit eligibility rules to keep the program sustainable. Fulfillment is handled by emailing support@kaelio.com. The .github/ISSUE_TEMPLATE/ forms give structure to bug reports and feature requests, and config.yml routes questions to the KTX Slack instead of GitHub Discussions (matching the routing established in docs-site/.../support.mdx). The triage-issues workflow applies a needs-triage label only when the issue author isn't OWNER, MEMBER, or COLLABORATOR — so internal issues stay clean while external contributions get queued for maintainer review. The first 14 connector contribution issues (#161-174) have been filed using these labels and reward tiers. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * chore(community): add SECURITY.md Documents the private reporting channel (GitHub Security Advisories with support@kaelio.com as fallback), what reporters should include, and the supported-version policy. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
31 lines
1 KiB
Markdown
31 lines
1 KiB
Markdown
# Security Policy
|
|
|
|
## Reporting a vulnerability
|
|
|
|
If you believe you've found a security vulnerability in KTX, please report it
|
|
**privately** through GitHub Security Advisories:
|
|
|
|
[Report a vulnerability](https://github.com/Kaelio/ktx/security/advisories/new)
|
|
|
|
If you cannot use GitHub Security Advisories, email `support@kaelio.com`
|
|
instead. Please do **not** open a public issue, post in the KTX Slack, or
|
|
share details elsewhere until we have published a fix.
|
|
|
|
When reporting, please include:
|
|
|
|
- A description of the issue and its impact
|
|
- Steps to reproduce
|
|
- The KTX version affected
|
|
|
|
## What to expect
|
|
|
|
- We will acknowledge your report within a few business days.
|
|
- We will work with you to verify the issue and develop a fix.
|
|
- We will credit you in the resulting advisory unless you prefer to remain
|
|
anonymous.
|
|
|
|
## Supported versions
|
|
|
|
We provide security fixes for the latest released version of
|
|
[`@kaelio/ktx`](https://www.npmjs.com/package/@kaelio/ktx). Older versions
|
|
may receive fixes at the maintainers' discretion.
|