We release patches for security vulnerabilities in the following versions:

We take the security of create-markdown seriously. If you discover a security vulnerability, please follow these steps:

1. Do not open a public GitHub issue for security vulnerabilities
2. Email your findings to val@viewdue.ai
3. Alternatively, use GitHub's private vulnerability reporting

Please provide as much information as possible to help us understand and resolve the issue:

• Type of vulnerability (e.g., XSS, injection, denial of service)
• Full paths of affected source files
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if available)
• Impact assessment and potential severity

• Initial Response: We will acknowledge receipt of your report within 48 hours
• Status Updates: We will keep you informed of our progress toward a fix
• Resolution Timeline: We aim to resolve critical vulnerabilities within 7 days
• Disclosure: We will coordinate with you on the timing of public disclosure

We consider security research conducted in accordance with this policy to be:

• Authorized concerning any applicable anti-hacking laws
• Authorized concerning any relevant anti-circumvention laws
• Exempt from restrictions in our Terms of Service that would interfere with conducting security research

We will not pursue civil action or initiate a complaint to law enforcement for accidental, good-faith violations of this policy.

When using create-markdown in your projects:

1. Sanitize User Input: Always sanitize markdown content from untrusted sources before rendering
2. Treat Mermaid as Trusted by Default: Use mermaidPlugin({ config: { securityLevel: 'strict' } }) when diagram text can come from users
3. Keep Dependencies Updated: Regularly update to the latest version to receive security patches
4. Content Security Policy: Implement appropriate CSP headers when rendering markdown in browsers
5. Review Generated HTML: Be cautious with HTML output, especially when allowing raw HTML in markdown

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).