feat: add security finding issue template #3
There are no files selected for viewing
This file contains hidden or 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,81 @@ | ||
| name: Security Finding | ||
| description: Report an automated security scanner finding (for maintainers) | ||
| title: "[security] " | ||
| labels: ["security/triage-needed"] | ||
| body: | ||
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| **This template is for automated scanner findings reviewed by maintainers.** | ||
| If you are an external reporter, please use [Private Vulnerability Reporting](https://github.com/cozystack/cozystack/security/advisories/new) or email cncf-cozystack-security@lists.cncf.io instead. | ||
| - type: input | ||
| id: cve | ||
| attributes: | ||
| label: CVE ID | ||
| placeholder: CVE-YYYY-NNNNN | ||
| validations: | ||
| required: true | ||
|
Comment on lines
+11
to
+17
There was a problem hiding this comment. The - type: input
id: vulnerability_id
attributes:
label: Vulnerability ID
placeholder: "e.g., CVE-YYYY-NNNNN or GHSA-xxxx-xxxx-xxxx"
validations:
required: true |
||
| - type: dropdown | ||
| id: severity | ||
| attributes: | ||
| label: Severity | ||
| options: | ||
| - Critical | ||
| - High | ||
| - Medium | ||
| - Low | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: package | ||
| attributes: | ||
| label: Affected package | ||
| placeholder: "e.g., libcrypto3, stdlib, redis" | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: installed_version | ||
| attributes: | ||
| label: Installed version | ||
| placeholder: "e.g., 3.5.1-r0" | ||
| - type: input | ||
| id: fixed_version | ||
| attributes: | ||
| label: Fixed version | ||
| placeholder: "e.g., 3.5.5-r0 (or 'none available')" | ||
| - type: textarea | ||
| id: affected_components | ||
| attributes: | ||
| label: Affected Cozystack components | ||
| placeholder: | | ||
| - packages/system/velero | ||
| - packages/apps/postgres | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: description | ||
| attributes: | ||
| label: Description | ||
| placeholder: Brief description of the vulnerability and its impact | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: references | ||
| attributes: | ||
| label: References | ||
| placeholder: | | ||
| - https://nvd.nist.gov/vuln/detail/CVE-YYYY-NNNNN | ||
| - https://github.com/advisories/GHSA-XXXX | ||
| - type: dropdown | ||
| id: triage_status | ||
| attributes: | ||
| label: Triage status | ||
| options: | ||
| - new (needs triage) | ||
| - confirmed | ||
| - false-positive | ||
| - accepted-risk | ||
| - in-progress | ||
| - fixed | ||
| validations: | ||
| required: true | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default title
[security]is very minimal. Providing a suggested format in the title field can help maintainers create consistent and searchable issue titles across the repository.