Thanks for helping make the Hugo Creator theme a more secure experience for everyone.

Chris takes the security of the theme seriously. Hugo is based on Static Content. This means that there are no identities (Authentication / Authorization) or backend databases to worry about. As a result, this means the attack surface area is smaller, so there are fewer things to worry about.

Even so, there are several recommended practices that can be adopted. Content Security Policies are built-in to the Hugo Creator theme. CodeQL and other static analysis tools are adopted throughout the repositories. However, things can always slip through. If you spot anything, please get in touch.

If you believe you have found a security vulnerability in the Hugo Creator theme source code, please report it to us through coordinated disclosure.

Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

Instead, please drop a direct message on Twitter (@reddobowen).

Please include as much of the information listed below as you can to help us better understand and resolve the issue:

• The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting)
• Full paths of source file(s) related to the manifestation of the issue
• The location of the affected source code (tag/branch/commit or direct URL)
• Any special configuration required to reproduce the issue
• Step-by-step instructions to reproduce the issue
• Proof-of-concept or exploit code (if possible)
• Impact of the issue, including how an attacker might exploit the issue

This information will help triage your report more quickly.