-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: Update project name to Tomato Timer CLI in CONTRIBUTING.md and…
… SECURITY.md
- Loading branch information
1 parent
dfa4dc3
commit 93a1a71
Showing
2 changed files
with
12 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,11 +2,11 @@ | |
|
||
## Reporting a Vulnerability | ||
|
||
If you discover a security vulnerability in the Tomato Clock CLI project, please report it to our security team at <[email protected]>. We take security issues seriously and appreciate your efforts in responsibly disclosing any vulnerabilities. | ||
If you discover a security vulnerability in the Tomato Timer CLI project, please report it to our security team at <[email protected]>. We take security issues seriously and appreciate your efforts in responsibly disclosing any vulnerabilities. | ||
|
||
## Supported Versions | ||
|
||
The following versions of Tomato Clock CLI are currently supported with security updates: | ||
The following versions of Tomato Timer CLI are currently supported with security updates: | ||
|
||
- Version 1.0.0 and above | ||
|
||
|
@@ -18,17 +18,17 @@ If the vulnerability is confirmed, we will follow these steps: | |
|
||
1. Develop a patch or fix for the vulnerability. | ||
2. Test the patch thoroughly to ensure it resolves the issue. | ||
3. Release the patch as a new version of Tomato Clock CLI. | ||
3. Release the patch as a new version of Tomato Timer CLI. | ||
4. Notify users about the vulnerability and provide instructions on how to update to the latest secure version. | ||
|
||
## Bug Bounty Program | ||
|
||
We currently do not have a bug bounty program in place for the Tomato Clock CLI project. However, we appreciate and value any security-related contributions from the community. If you discover a vulnerability, please follow the reporting process mentioned above. | ||
We currently do not have a bug bounty program in place for the Tomato Timer CLI project. However, we appreciate and value any security-related contributions from the community. If you discover a vulnerability, please follow the reporting process mentioned above. | ||
|
||
## Responsible Disclosure | ||
|
||
We kindly request that you refrain from publicly disclosing any vulnerabilities until we have had sufficient time to address them. We strive to provide timely updates and fixes to ensure the security of our users. | ||
|
||
## Contact | ||
|
||
If you have any questions or concerns regarding the security of Tomato Clock CLI, please contact our security team at <[email protected]>. | ||
If you have any questions or concerns regarding the security of Tomato Timer CLI, please contact our security team at <[email protected]>. |