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
Copy file name to clipboardExpand all lines: SECURITY.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,8 +6,8 @@ We release patches for security vulnerabilities in the following versions:
6
6
7
7
| Version | Supported |
8
8
| ------- | ------------------ |
9
-
|1.x.x |:white_check_mark:|
10
-
| < 1.0 |:x:|
9
+
|2.x.x |:white_check_mark:|
10
+
| < 2.0 |:x:|
11
11
12
12
## Reporting a Vulnerability
13
13
@@ -16,7 +16,7 @@ We take the security of create-markdown seriously. If you discover a security vu
16
16
### How to Report
17
17
18
18
1.**Do not** open a public GitHub issue for security vulnerabilities
19
-
2. Email your findings to **val@viewdue.ai** (replace with your actual security email)
19
+
2. Email your findings to **val@viewdue.ai**
20
20
3. Alternatively, use [GitHub's private vulnerability reporting](https://github.com/BunsDev/create-markdown/security/advisories/new)
21
21
22
22
### What to Include
@@ -51,10 +51,11 @@ We will not pursue civil action or initiate a complaint to law enforcement for a
51
51
When using create-markdown in your projects:
52
52
53
53
1.**Sanitize User Input**: Always sanitize markdown content from untrusted sources before rendering
54
-
2.**Keep Dependencies Updated**: Regularly update to the latest version to receive security patches
55
-
3.**Content Security Policy**: Implement appropriate CSP headers when rendering markdown in browsers
56
-
4.**Review Generated HTML**: Be cautious with HTML output, especially when allowing raw HTML in markdown
54
+
2.**Treat Mermaid as Trusted by Default**: Use `mermaidPlugin({ config: { securityLevel: 'strict' } })` when diagram text can come from users
55
+
3.**Keep Dependencies Updated**: Regularly update to the latest version to receive security patches
56
+
4.**Content Security Policy**: Implement appropriate CSP headers when rendering markdown in browsers
57
+
5.**Review Generated HTML**: Be cautious with HTML output, especially when allowing raw HTML in markdown
57
58
58
59
## Acknowledgments
59
60
60
-
We appreciate the security research community's efforts in helping keep create-markdown secure. Contributors who report valid security issues will be acknowledged here (with their permission).
61
+
We appreciate the security research community's efforts in helping keep create-markdown secure. Contributors who report valid security issues will be acknowledged here (with their permission).
0 commit comments