We take security seriously in the Vue 3 Fancy Template. Please help us maintain safe and secure projects for everyone.

Please DO NOT report security vulnerabilities through public GitHub issues. Instead, use either:

1. GitHub Security Advisory:
   Open a security advisory

2. Email:
   ashsajal@yahoo.com

• Detailed description of the vulnerability
• Steps to reproduce
• Potential impact assessment
• Any suggested mitigations

• ⏳ Initial response within 48 hours
• 📅 Regular status updates
• 🛠 Critical fixes within 14 days of confirmation

• Regular dependency updates (npm audit)
• Pinia state management security patterns
• PrimeVue component secure configurations
• TypeScript strict mode enforcement
• CI/CD security checks (npm audit in workflows)

1. Dependencies:

   • Regular npm audit checks
   • Pinned dependency versions in lockfile
   • Security-focused dependency updates

2. Code Practices:

   • Input sanitization for user-provided data
   • Secure Vue template practices
   • Type-safe state management with Pinia
   • CSP-compliant frontend patterns

3. CI/CD:

   • Automated security scanning
   • Dependency vulnerability checks
   • Linting for security anti-patterns

Accepted vulnerabilities will be:

1. Patched in a timely manner
2. Disclosed through:
   • GitHub Security Advisory
   • Release notes
   • Project documentation
3. Credited to reporter (unless anonymous)

This template relies on:

• Vue 3 (security advisories: https://github.com/vuejs/core/security)
• PrimeVue (security: https://primefaces.org/primevue/security)
• Pinia (security: https://github.com/vuejs/pinia/security)
• Tailwind CSS (security: https://github.com/tailwindlabs/tailwindcss/security)

Always:

• Keep dependencies updated
• Monitor dependency security advisories
• Use npm audit regularly

We gratefully acknowledge security researchers who responsibly disclose vulnerabilities.
See contributors who helped improve security.

🔍 Need More Info?
See GitHub's Security Documentation