Skip to content

Security: PEPETII/UI-And-AI-Showcase

Security

SECURITY.md

Security Policy

Supported Versions

We release patches for security vulnerabilities for the following versions:

Version Supported
1.0.x βœ…

Reporting a Vulnerability

We take security seriously. If you discover a security vulnerability, please follow these steps:

πŸ”’ Private Disclosure

Do NOT create a public GitHub issue for security vulnerabilities.

Instead, please report security issues by emailing: Use this repository's GitHub Security Advisories / private vulnerability reporting feature.

πŸ“ What to Include

Your report should include:

  1. Description β€” Clear explanation of the vulnerability
  2. Steps to Reproduce β€” Detailed steps to reproduce the issue
  3. Impact Assessment β€” Potential impact and severity
  4. Suggested Fix β€” If you have recommendations (optional)
  5. Your Contact Info β€” So we can follow up

⏱️ Response Timeline

  • Initial Response: Within 48 hours
  • Status Update: Within 7 days
  • Fix Timeline: Varies by severity
    • Critical: 1-7 days
    • High: 7-30 days
    • Medium: 30-90 days
    • Low: Best effort

πŸ† Recognition

We appreciate responsible disclosure. With your permission, we'll:

  • Credit you in our CHANGELOG
  • List you in our security acknowledgments

πŸ›‘οΈ Security Best Practices for Users

  1. Always use HTTPS when deploying
  2. Keep dependencies updated (npm audit regularly)
  3. Don't commit .env files with sensitive data
  4. Use Content Security Policy headers
  5. Validate user inputs if you fork and add backend features

Common Concerns

localStorage & Security

This project uses localStorage for:

  • User preferences (theme, language)
  • Favorites list
  • Vote history

Note: No sensitive data is stored. All data stays client-side.

Third-party CDN Scripts

We use CDN scripts for:

  • Alpine.js (reactivity)
  • i18next (internationalization)
  • Supabase (optional backend)

All scripts use SRI (Subresource Integrity) hashes where available.

πŸ” Known Safe Practices

  • βœ… No server-side code execution
  • βœ… No database credentials in client code
  • βœ… No authentication tokens stored insecurely
  • βœ… CORS properly configured
  • βœ… XSS protection via CSP headers (recommended)

Thank you for helping keep UI and AI secure! πŸ™

There aren't any published security advisories