We take the security of Typogenesis seriously. If you believe you have found a security vulnerability, please report it to us as described below.

Please do NOT report security vulnerabilities through public GitHub issues.

Instead, please report them via GitHub's private vulnerability reporting.

You should receive a response within 48 hours. If for some reason you do not, please follow up via email to ensure we received your original message.

Please include the following information:

• Type of issue (e.g., XSS, buffer overflow, injection, etc.)
• 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 it

We prefer all communications to be in English.

This project follows these security practices:

• No sensitive data in code: The project is a frontend-only demo with no API keys, tokens, or credentials
• Dependency management: Regular npm audit checks and dependency updates
• TypeScript strict mode: Catches potential type-related vulnerabilities
• No eval() or innerHTML: DOM manipulation uses safe APIs (textContent, explicit element creation)
• CSP-friendly: No inline scripts that would violate strict Content Security Policies

This security policy applies to:

• The main codebase in the src/ directory
• Build configuration (vite.config.ts, tsconfig.json)
• Dependencies listed in package.json

Out of scope:

• Third-party dependencies (report directly to their maintainers)
• Google Fonts loading (handled by browser security)
• Vercel deployment infrastructure (managed by Vercel)

We will acknowledge receipt of your vulnerability report and send you regular updates about our progress. We appreciate your responsible disclosure and will credit you in our release notes if you wish.

Upon receiving a vulnerability report:

1. We will confirm receipt within 48 hours
2. We will assess the vulnerability and determine its impact
3. We will develop and test a fix
4. We will release the fix and publish a security advisory
5. We will credit the reporter (if desired)

Thank you for helping keep Typogenesis and its users safe!