feat: Add SECURITY and issue templates

This commit is contained in:
Jesse Wierzbinski 2024-08-28 03:23:55 +02:00
parent 4cee3f8d21
commit 537efe5340
No known key found for this signature in database
3 changed files with 92 additions and 0 deletions

39
.github/ISSUE_TEMPLATE/bug_report.md vendored Normal file
View file

@ -0,0 +1,39 @@
---
name: Bug report
about: Create a report to help us improve
title: ''
labels: bug
assignees: ''
---
## Describe the bug
A clear and concise description of what the bug is.
## Steps to reproduce
Steps to reproduce the behavior, such as a cURL command, HTTP request, situation or code repository
## Expected behavior
A clear and concise description of what you expected to happen.
## Screenshots
If applicable, add screenshots to help explain your problem.
## Logs
Please upload logs onto a service like [Pastebin](https://pastebin.com/) or [Hastebin](https://hastebin.com/) and paste the link here. Don't paste the logs directly into the GitHub issue, as it just looks ugly and is hard to read.
## Environment
- OS: [e.g. Fedora 39]
- Runtime version: [e.g. Node.js 16.13.0]
- Database version: [e.g. PostgreSQL 14.1]
- Project commit ID or version
## Additional context
Add any other context about the problem here.

View file

@ -0,0 +1,28 @@
---
name: Feature request
about: Suggest an idea for this project
title: ''
labels: enhancement
assignees: ''
---
## Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is, such as "I'm always frustrated when [...]" or "I can't do [...]"
## Describe the solution you'd like
What would you like to see implemented?
## Describe alternatives you've considered
If applicable, describe any alternative solutions or features you've considered.
## Additional context
Add any other context or screenshots about the feature request here.
## Are you willing to work on this feature?
If you are willing to work on this feature, please say so here.

25
SECURITY.md Normal file
View file

@ -0,0 +1,25 @@
# Security Policy
## Supported Versions
The latest versions of all Versia software are supported with security updates. If manpower allows, we will backport security patches to older versions of the software.
## Reporting a Vulnerability
If you find a vulnerability, please report it to a member of the core team:
- [Jesse Wierzbinski - **`@CPlusPatch`**](https://github.com/CPlusPatch)
- Contact info on my [website](https://cpluspatch.com/contact)
- [April John - **`cutestnekoaqua`**](https://github.com/cutestnekoaqua)
- [Anna - **`@TheDevMinerTV`**](https://github.com/TheDevMinerTV)
- Contact info on my [website](https://devminer.xyz/contact)
Please do not report vulnerabilities publicly until they have been patched. If you would like to be credited for your discovery, you can include your name or other identifying characteristics in the report.
## Vulnerability Disclosure Policy
Versia is an open-source project, and as such, we welcome security researchers to audit our code and report vulnerabilities. We will do our best to patch vulnerabilities as quickly as possible, and will credit researchers for their discoveries if they wish to be credited.
For security reasons, we ask that you do not publicly disclose vulnerabilities until they have been patched. We will do our best to patch vulnerabilities as quickly as possible, and will credit researchers for their discoveries if they wish to be credited.
Thank you for helping to keep Versia software secure! :3