We currently support the following versions of the GlimWorld site:

If you discover a security vulnerability in the GlimWorld site or repository, please report it responsibly.

Do NOT open a public issue. Instead, contact us:

• 📧 Email: Use our contact form
• 📝 Subject line: "Security Vulnerability Report"

Please provide:

• Description of the vulnerability
• Steps to reproduce
• Potential impact
• Any suggested fixes (optional)

• We aim to acknowledge reports within 48 hours
• We'll assess the vulnerability and provide a timeline for a fix
• We'll provide updates on the fix within 7 days
• Once fixed, we'll credit you in the security advisory (unless you prefer to remain anonymous)

For GlimWorld community members:

• Keep your browser and extensions up to date
• Never share your personal information publicly
• Don't share sensitive information through Gimkit quizzes
• Use the support contact form for sensitive issues
• Report suspicious activity or spam immediately
• Keep your GitHub/Padlet accounts secure with strong, unique passwords

This policy covers:

• The GlimWorld GitHub Pages site
• This repository and its code
• Links and integrations (Padlet, contact form)

GlimWorld uses the following tools and services:

• GitHub Actions for CI/CD
• Node.js for build tools
• Standard web technologies (HTML, CSS, JavaScript)

We regularly audit dependencies for vulnerabilities using:

• npm audit
• Dependabot alerts
• Manual security reviews

Thank you for helping keep GlimWorld safe and secure! 🔒