PrivateCoffee/quackscape
PrivateCoffee/quackscape
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

feat: add initial SECURITY.md for project

Browse source 
guidelines

Introduced a Security Policy in the newly added SECURITY.md file,
outlining the project's current security status, cautioning users about
its early-stage development, and providing guidance on reporting
vulnerabilities. This establishes a clear protocol for communicating and
handling security concerns, ensuring contributors and users have a
direct channel for raising security issues with the Private.coffee
security team. This move reflects a proactive approach to security and
transparency as the project evolves.
This commit is contained in:
Kumi 2024-03-15 14:33:14 +01:00
parent 4779f89513
commit 0888e6132a
Signed by: kumi
GPG key ID: ECBCC9082395383F
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
SECURITY.md Normal file
View file

@ -0,0 +1,9 @@
# Security Policy
Please note that Quackscape is still in the early stages of development and is not yet ready for production use, so we do not guarantee the security of the project at this time. We are working to improve the security of the project, and we will update this policy as the project matures.
## Reporting a Vulnerability
If you find a security vulnerability in this project, please get in touch with the Private.coffee security team. You can find contact details at [security.private.coffee](https://security.private.coffee).
For anything non-security related, please use issues in the [Private.coffee Git](https://git.private.coffee/PrivateCoffee/quackscape/issues) or [GitHub](https://github.com/PrivateCoffee/quackscape/issues).