Skip to content

Commit ff9ff0a

Browse files
committed
doc: Update security policy
1 parent 4f8e923 commit ff9ff0a

File tree

1 file changed

+62
-40
lines changed

1 file changed

+62
-40
lines changed

SECURITY.md

Lines changed: 62 additions & 40 deletions
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,62 @@
1-
<!doctype html>
2-
<html lang="en" class="h-100">
3-
4-
<head>
5-
<meta charset="utf-8">
6-
<meta name="viewport" content="width=device-width, initial-scale=1">
7-
<link href="https://cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/css/bootstrap.min.css" rel="stylesheet"
8-
integrity="sha384-T3c6CoIi6uLrA9TneNEoa7RxnatzjcDSCmG1MXxSR1GAsXEV/Dwwykc2MPK8M2HN" crossorigin="anonymous">
9-
<title>404</title>
10-
</head>
11-
12-
<body class="h-100">
13-
<div class="d-flex align-items-center justify-content-center h-100">
14-
<div class="">
15-
<h1>404 Not Found</h1>
16-
<p> Sorry, the page you are looking for could not be found.</p>
17-
</div>
18-
</div>
19-
20-
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.2/dist/js/bootstrap.bundle.min.js" integrity="sha384-C6RzsynM9kWDrMNeT87bh95OGNyZPhcTNXj1NW7RuBCsyN/o0jlpcV8Qyq46cDfL" crossorigin="anonymous" type="4fc775d50a9a5411611f423e-text/javascript"></script>
21-
<script type="4fc775d50a9a5411611f423e-text/javascript">
22-
const darkModeMediaQuery = window.matchMedia('(prefers-color-scheme: dark)');
23-
24-
if (darkModeMediaQuery.matches) {
25-
document.documentElement.setAttribute('data-bs-theme', 'dark');
26-
} else {
27-
document.documentElement.setAttribute('data-bs-theme', 'light');
28-
}
29-
30-
darkModeMediaQuery.addEventListener('change', (event) => {
31-
if (event.matches) {
32-
document.documentElement.setAttribute('data-bs-theme', 'dark');
33-
} else {
34-
document.documentElement.setAttribute('data-bs-theme', 'light');
35-
}
36-
});
37-
</script>
38-
<script src="/cdn-cgi/scripts/7d0fa10a/cloudflare-static/rocket-loader.min.js" data-cf-settings="4fc775d50a9a5411611f423e-|49" defer></script></body>
39-
40-
</html>
1+
# Security Policy
2+
3+
## Supported Versions
4+
5+
The following table outlines the versions of the project that are currently supported with security & feature updates:
6+
7+
> [!NOTE]
8+
> Once a version starts its security phase, it will no longer receive feature updates. Only critical bug fixes and security updates will be provided.
9+
10+
| Package Version | Umbraco Version | Security Phase Start | End of Life |
11+
| ---------------------------------------------------------------------------------- | --------------- | -------------------- | ----------- |
12+
| [10.x](https://github.com/jcdcdev/Umbraco.Community.FileSystemProviders.B2/tree/v10) | 10 | 2024-06-16 | 2025-06-16 |
13+
| [13.x](https://github.com/jcdcdev/Umbraco.Community.FileSystemProviders.B2/tree/v13) | 13 | 2025-12-14 | 2026-12-14 |
14+
| [14.x](https://github.com/jcdcdev/Umbraco.Community.FileSystemProviders.B2/tree/v14) | 14 | 2025-03-02 | 2025-05-30 |
15+
| [15.x](https://github.com/jcdcdev/Umbraco.Community.FileSystemProviders.B2/tree/v15) | 15 | 2025-08-14 | 2025-11-14 |
16+
## Unsupported Versions
17+
18+
| Package Version | Umbraco Version | End of Life |
19+
| ---------------------------------------------------------------------------------- | --------------- | ----------- |
20+
| [12.x](https://github.com/jcdcdev/Umbraco.Community.FileSystemProviders.B2/tree/v12) | 12 | 2024-06-29 |
21+
22+
23+
## Future Support
24+
25+
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.
26+
27+
> [!NOTE]
28+
> Visit [jcdc.dev/blog/umbraco-version-information](https://jcdc.dev/blog/umbraco-version-information) for more information on Umbraco versions.
29+
30+
## Reporting a Vulnerability
31+
32+
If you discover a vulnerability in this project, please follow one of these steps to report it:
33+
34+
- Create an [issue](https://github.com/jcdcdev/Umbraco.Community.FileSystemProviders.B2/security/advisories/new)
35+
- Contact the project author privately at [jcdc.dev/contact](https://jcdc.dev/contact)
36+
37+
### Details
38+
39+
Include as much information as possible about the vulnerability, including:
40+
41+
- Steps to reproduce
42+
- Potential impact
43+
- Any suggested fixes
44+
45+
### Acknowledgment
46+
47+
You will receive an acknowledgment of your report as soon as possible.
48+
49+
> [!NOTE]
50+
> Response times may vary depending on other commitments.
51+
52+
### Resolution
53+
54+
Once the vulnerability is confirmed, project maintainers will work to resolve it as quickly as possible.
55+
56+
You will be notified once the issue has been resolved or rejected.
57+
58+
> [!TIP]
59+
> If the vulnerability is accepted, you will receive credit in the release notes.
60+
61+
Thank you for helping to keep this project secure!
62+

0 commit comments

Comments
 (0)