You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
⚠️ **Please DO NOT report security vulnerabilities here.** Instead, use the GitHub Security Advisories feature to report them privately and securely. This helps us address issues responsibly without exposing them publicly.
15
16
16
-
- type: textarea
17
-
id: security-issue-description
18
-
attributes:
19
-
label: Describe the security issue
20
-
description: Provide a clear and concise description of what the security issue is, without including sensitive details.
21
-
placeholder: Describe the security issue...
22
-
validations:
23
-
required: true
24
-
25
-
- type: textarea
26
-
id: steps-to-reproduce
27
-
attributes:
28
-
label: To Reproduce
29
-
description: |
30
-
Steps to reproduce the security issue:
31
-
1. Navigate to...
32
-
2. Perform action...
33
-
3. Observe outcome...
34
-
placeholder: |
35
-
1. Navigate to...
36
-
2. Perform action...
37
-
3. Observe outcome...
38
-
validations:
39
-
required: true
40
-
41
-
- type: textarea
42
-
id: expected-behaviour
43
-
attributes:
44
-
label: Expected behaviour
45
-
description: Describe what you expected to happen without the security flaw.
46
-
placeholder: What did you expect to happen?
47
-
validations:
48
-
required: true
49
-
50
-
- type: textarea
51
-
id: media-prove
17
+
- type: markdown
52
18
attributes:
53
-
label: Media prove
54
-
description: If applicable, add screenshots or videos that help explain your issue, ensuring no sensitive data is displayed.
55
-
placeholder: Upload files or paste links here...
56
-
validations:
57
-
required: false
19
+
value: >
20
+
GitHub Advisories do not automatically notify maintainers, so by using the advisories, you help maintain confidentiality while ensuring the issue is documented and tracked properly.
58
21
59
-
- type: textarea
60
-
id: environment
22
+
- type: markdown
61
23
attributes:
62
-
label: Your environment
63
-
description: |
64
-
Provide detailed information about your environment to help us replicate the issue:
65
-
* OS: [e.g. Ubuntu]
66
-
* PHP version: [e.g. 8.2.2]
67
-
* Package version: [e.g. 1.0.0]
68
-
* Any relevant environment details
69
-
placeholder: List your environment details here...
70
-
validations:
71
-
required: false
24
+
value: 'To create a new advisory, go to: [Create Security Advisory](https://github.com/wayofdev/laravel-package-tpl/security/advisories/new)'
72
25
73
26
- type: textarea
74
-
id: additional-context
27
+
id: github-advisory-url
75
28
attributes:
76
-
label: Additional context
77
-
description: Add any other context about the problem here, ensuring no sensitive data is included.
78
-
placeholder: Any additional information...
29
+
label: Your GitHub Advisory URL
30
+
description: Optionally, you can paste the URL of the GitHub Security Advisory you have created here for reference.
31
+
placeholder: Paste the GitHub Security Advisory URL here...
Copy file name to clipboardExpand all lines: .github/SECURITY.md
+13-5Lines changed: 13 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Thank you for helping keep `wayofdev/laravel-package-tpl` and its users safe. We
6
6
7
7
## 🙋♂️ Supported Versions
8
8
9
-
Only certain versions of `wayofdev/laravel-package-tpl` are currently being maintained with security updates. Below is a list of supported versions that receive security updates:
9
+
Only certain versions of `wayofdev/laravel-package-tpl` are currently being maintained with security updates. Please use or upgrade to one of these supported versions:
10
10
11
11
| Version | Supported |
12
12
|---------|--------------------|
@@ -16,7 +16,7 @@ Please ensure that you are using one of these supported versions before reportin
16
16
17
17
<br>
18
18
19
-
## 🗑️ Unsupported Versions
19
+
## 🗜️ Unsupported Versions
20
20
21
21
Versions listed below are no longer supported with security updates. We recommend upgrading to a supported version as soon as possible:
22
22
@@ -28,12 +28,20 @@ Versions listed below are no longer supported with security updates. We recommen
28
28
29
29
## 🚨 Reporting a Vulnerability
30
30
31
-
We take all security bugs in `wayofdev/laravel-package-tpl` seriously. Thank you for improving the security of this project. We appreciate your efforts and responsible disclosure and will make every effort to acknowledge your contributions.
31
+
We take all security bugs in `wayofdev/laravel-package-tpl` seriously. Please follow the instructions below to report security vulnerabilities.
32
32
33
33
### → How to Report a Vulnerability
34
34
35
-
1.**Direct Contact**: For highly sensitive information, please email us directly at `[email protected]` with the subject line "SECURITY - Vulnerability Report". This will be treated with the highest priority.
35
+
1.**GitHub Security Advisories**: Please report security issues directly through our GitHub Security Advisories page: https://github.com/wayofdev/laravel-package-tpl/security/advisories/new. This ensures that sensitive information is handled confidentially.
36
36
37
-
2.**GitHub Issues**: For vulnerabilities that do not immediately affect the security of the application or its users, such as those found in non-critical systems, please report them through our GitHub issues. Make sure to use the `⚠️ Security Report` issue template. Please do not include sensitive information in GitHub issues. Detailed instructions about how to fill this report are included within the issue template itself.
37
+
2.**Empty Security Issue**: After submitting through GitHub Security Advisories, please also create an empty security issue to alert us, as GitHub Advisories do not send automatic notifications. This can be done here: https://github.com/wayofdev/laravel-package-tpl/issues/new?assignees=&labels=type%3A+bug%2Cpriority%3A+high%2Ctype%3A+security&projects=&template=5-security-report.yml&title=%5BSecurity%5D%3A+
38
+
39
+
3.**Direct Contact**: For highly sensitive information, in addition to the GitHub Security Advisories, please email us directly at `[email protected]` with the subject line "SECURITY - Vulnerability Report". This will be treated with the highest priority.
40
+
41
+
Please do not discuss potential security issues in public forums or through our public GitHub issues tracker.
42
+
43
+
## ❌ Third-Party Bug Bounty Platforms
44
+
45
+
At this moment, we DO NOT accept reports from third-party bug bounty platforms to minimize risk. All vulnerability reports should come through the specified channels above.
0 commit comments