Look, this is a documentation repo with markdown files. The attack surface is pretty small. But if you find something, I want to know.

Please don't open a public issue for security vulnerabilities.

Instead, use one of these methods:

1. GitHub Security Advisory (Recommended): Report a security vulnerability
2. Email: 20714140+JacobPEvans@users.noreply.github.com
3. GitHub: Reach out to @JacobPEvans on GitHub directly

• Description of the vulnerability
• Steps to reproduce
• Potential impact
• Any suggested fixes (if you have them)

I maintain this project in my spare time, so:

• Acknowledgment: Within a week, usually faster
• Assessment: Within two weeks
• Fix: Depends on severity and complexity

For critical issues, I'll prioritize accordingly. For theoretical edge cases in markdown parsing, we might take our time.

• Secrets accidentally committed (unlikely, but possible)
• Malicious content in instructions that could harm users
• Anything that could compromise systems using these instructions

• Markdown rendering quirks
• Broken links
• Typos (unless they cause the AI to do something dangerous)

Thanks for helping keep this project safe.