Skip to content

Commit 95665c7

Browse files
committed
docs: add SECURITY.md
1 parent 5fa51be commit 95665c7

File tree

1 file changed

+56
-0
lines changed

1 file changed

+56
-0
lines changed

SECURITY.md

Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
The following table outlines the versions of the project that are currently supported with security updates:
6+
7+
| Version | Supported | Umbraco Version |
8+
| ------------------------------------------------------------------------------------ | --------- | --------------- |
9+
| [15.x](https://github.com/jcdcdev/jcdcdev.Umbraco.ExtendedMarkdownEditor/tree/v15) || 15 |
10+
| [14.x](https://github.com/jcdcdev/jcdcdev.Umbraco.ExtendedMarkdownEditor/tree/v14) || 14 |
11+
| [13.x](https://github.com/jcdcdev/jcdcdev.Umbraco.ExtendedMarkdownEditor/tree/v13) || 13 |
12+
| [10.x](https://github.com/jcdcdev/jcdcdev.Umbraco.ExtendedMarkdownEditor/tree/v10) || 10 |
13+
| [12.x](https://github.com/jcdcdev/jcdcdev.Umbraco.ExtendedMarkdownEditor/tree/v12) || 12 |
14+
| [0.1.x](https://github.com/jcdcdev/jcdcdev.Umbraco.ExtendedMarkdownEditor/tree/main) || 11 |
15+
16+
17+
## Future Support
18+
19+
Project maintainers plan to support all STS (Short-Term Support) and LTS (Long-Term Support) versions of Umbraco. However, exact release dates cannot be guaranteed.
20+
21+
> [!NOTE]
22+
> Visit [jcdc.dev/blog/umbraco-version-information](https://jcdc.dev/blog/umbraco-version-information) for more information on Umbraco versions.
23+
24+
## Reporting a Vulnerability
25+
26+
If you discover a vulnerability in this project, please follow one of these steps to report it:
27+
28+
- Create an [issue](https://github.com/jcdcdev/jcdcdev.Umbraco.ExtendedMarkdownEditor/security/advisories/new)
29+
- Contact the project author privately at [jcdc.dev/contact](https://jcdc.dev/contact)
30+
31+
### Details
32+
33+
Include as much information as possible about the vulnerability, including:
34+
35+
- Steps to reproduce
36+
- Potential impact
37+
- Any suggested fixes
38+
39+
40+
### Acknowledgment
41+
42+
You will receive an acknowledgment of your report as soon as possible.
43+
44+
> [!NOTE]
45+
> Response times may vary depending on other commitments.
46+
47+
### Resolution
48+
49+
Once the vulnerability is confirmed, project maintainers will work to resolve it as quickly as possible.
50+
51+
You will be notified once the issue has been resolved or rejected.
52+
53+
> [!TIP]
54+
> If the vulnerability is accepted, you will receive credit in the release notes.
55+
56+
Thank you for helping to keep this project secure!

0 commit comments

Comments
 (0)