Fixed: Resolve Markdown linting issues in CONTRIBUTING.md and SECURITY.md

- Corrected Markdown formatting issues in CONTRIBUTING.md and SECURITY.md.
- Ensured files are properly linted for consistent styling and readability.

modified:   CONTRIBUTING.md
modified:   SECURITY.md
This commit is contained in:
GJS 2025-03-28 10:58:49 +01:00
parent 7f9322a524
commit cdb09686d9
No known key found for this signature in database
GPG Key ID: BE32D9EAF927E85B
2 changed files with 26 additions and 18 deletions

View File

@ -350,10 +350,10 @@ are stuck on.
### Recommended Pull Request Guideline
Before jumping into coding, it's recommended to initiate a discussion by
creating an empty pull request. This approach allows us to align on the direction
and scope of the feature, ensuring it doesn't conflict with existing or planned
work. It also provides an opportunity to identify potential pitfalls early on,
helping to avoid issues down the line.
creating an empty pull request. This approach allows us to align on the
direction and scope of the feature, ensuring it doesn't conflict with existing
or planned work. It also provides an opportunity to identify potential pitfalls
early on, helping to avoid issues down the line.
1. **Fork** the [Uptime-Kuma repository].
2. **Clone** your forked repository to your local machine.

View File

@ -2,29 +2,37 @@
## Reporting a Vulnerability
1. Please report security issues to https://github.com/louislam/uptime-kuma/security/advisories/new.
2. Please also create an empty security issue to alert me, as GitHub Advisories do not send a notification, I probably will miss it without this. https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md
1. Please report security issues to
<https://github.com/louislam/uptime-kuma/security/advisories/new>.
2. Please also create an empty security issue to alert me, as GitHub Advisories
do not send a notification, I probably will miss it without this.
<https://github.com/louislam/uptime-kuma/issues/new?assignees=&labels=help&template=security.md>
Do not use the public issue tracker or discuss it in public as it will cause more damage.
Do not use the public issue tracker or discuss it in public as it will cause
more damage.
## Do you accept other 3rd-party bug bounty platforms?
At this moment, I DO NOT accept other bug bounty platforms, because I am not familiar with these platforms and someone has tried to send a phishing link to me by doing this already. To minimize my own risk, please report through GitHub Advisories only. I will ignore all 3rd-party bug bounty platforms emails.
At this moment, I DO NOT accept other bug bounty platforms, because I am not
familiar with these platforms and someone has tried to send a phishing link to
me by doing this already. To minimize my own risk, please report through GitHub
Advisories only. I will ignore all 3rd-party bug bounty platforms emails.
## Supported Versions
### Uptime Kuma Versions
You should use or upgrade to the latest version of Uptime Kuma. All `1.X.X` versions are upgradable to the latest version.
You should use or upgrade to the latest version of Uptime Kuma. All `1.X.X`
versions are upgradable to the latest version.
### Upgradable Docker Tags
| Tag | Supported |
|-|-|
| 1 | :white_check_mark: |
| 1-debian | :white_check_mark: |
| latest | :white_check_mark: |
| debian | :white_check_mark: |
| 1-alpine | ⚠️ Deprecated |
| alpine | ⚠️ Deprecated |
| All other tags | ❌ |
| Tag | Supported |
| -------------- | ------------------ |
| 1 | :white_check_mark: |
| 1-debian | :white_check_mark: |
| latest | :white_check_mark: |
| debian | :white_check_mark: |
| 1-alpine | ⚠️ Deprecated |
| alpine | ⚠️ Deprecated |
| All other tags | ❌ |