Skip to content

Commit

Permalink
chore: Migrate security report into Issue form (#1486)
Browse files Browse the repository at this point in the history
* Create security_issue.yml

* Delete Security_issue.md
  • Loading branch information
tomkerkhove authored Feb 5, 2021
1 parent f493dee commit b7a1331
Show file tree
Hide file tree
Showing 2 changed files with 45 additions and 34 deletions.
34 changes: 0 additions & 34 deletions .github/ISSUE_TEMPLATE/Security_issue.md

This file was deleted.

45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/security_issue.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
name: Security Report 🔐
about: Report security vulnerability impacting users
labels: security
assignees: tomkerkhove
issue_body: true
inputs:
- type: textarea
attributes:
label: Report
description: "What is the vulnerability and how does it affect Promitor?
placeholder: "A clear and concise description of how the security issue affects this project"
- type: input
attributes:
label: Vulnerability Information
description: Are there official sources listing the vulnerability? For example, the National Vulnurability Database or similar.
required: false
- type: multi_select
attributes:
label: Affected Component(s)
description: What Promitor components are impacted?
required: true
choices:
- Resource Discovery
- Scraper
- type: input
attributes:
label: Affected Version(s)
description: What version(s) are impacted?
required: true
- type: textarea
attributes:
label: Vulnerability Migitation
description: "What are the options to mitigate the vulnerability?"
required: false
- type: textarea
attributes:
label: Vulnerability Fix
description: "What are the options to patch the vulnerability?"
required: false
- type: input
attributes:
label: Contact Details
description: How can we get in touch with you if we need more info?
required: false
placeholder: ex. email@example.com

0 comments on commit b7a1331

Please sign in to comment.