-
-
Notifications
You must be signed in to change notification settings - Fork 186
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'pterm:master' into add-feedback-password-prompter
- Loading branch information
Showing
81 changed files
with
209 additions
and
162 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
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
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 |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# PTerm Security Policy | ||
This security policy applies to the PTerm GitHub repository and outlines the process for reporting security issues and handling security incidents. The primary goal of this policy is to ensure the safety and integrity of the PTerm codebase and to minimize the impact of security incidents on our users. | ||
|
||
## 1. Overview | ||
PTerm is a command-line interface (CLI) tool library, and we believe the security risks associated with it are minimal. However, we recognize that vulnerabilities can still arise, and we are committed to addressing them promptly and transparently. | ||
|
||
## 2. Reporting Security Issues | ||
If you discover a security issue in PTerm, please follow these steps: | ||
|
||
Open a new issue in the PTerm GitHub repository, describing the security problem in detail. | ||
Do not disclose any sensitive information or exploit details in the issue, as PTerm is not considered to have any exploitable features. | ||
|
||
## 3. Vulnerable Dependencies | ||
If a dependency of PTerm is found to be vulnerable or infected and requires immediate updates, please follow these steps: | ||
|
||
1. Open a new issue in the PTerm GitHub repository, describing the vulnerable dependency and the need for an update. | ||
2. *Optional: Contact @MarvinJWendt directly via Twitter or Discord to alert them to the issue.* | ||
|
||
## 4. Incident Response | ||
Upon receiving a security report, the PTerm team will: | ||
|
||
1. Acknowledge receipt of the report and review the issue. | ||
2. Investigate the issue and determine the severity and impact. | ||
3. Develop and implement a fix or mitigation plan, as necessary. | ||
4. Update the PTerm repository and notify users, if applicable. |
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
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.