We actively support the following versions of the Developer Portfolio Dashboard:
| Version | Supported |
|---|---|
| 1.0.x | ✅ |
| < 1.0 | ❌ |
We take security vulnerabilities seriously. If you discover a security vulnerability, please follow these steps:
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Instead, please send an email to [security@yourproject.com] with the following information:
- A description of the vulnerability
- Steps to reproduce the issue
- Potential impact of the vulnerability
- Any suggested fixes (if you have them)
- We will acknowledge receipt of your vulnerability report within 48 hours
- We will provide a detailed response within 7 days indicating next steps
- We will keep you informed of our progress toward a fix
- We may ask for additional information or guidance
- We will work with you to understand and resolve the issue quickly
- We will credit you in our security advisory (unless you prefer to remain anonymous)
- We will coordinate the timing of any public disclosure
When contributing to this project, please follow these security guidelines:
- Never commit sensitive information like API keys, passwords, or tokens
- Use
.env.localfor local development secrets - Ensure
.env.localis in.gitignore
- Keep dependencies up to date
- Run
npm auditregularly to check for vulnerabilities - Use Dependabot to automate dependency updates
- Validate all user inputs
- Use parameterized queries to prevent SQL injection
- Implement proper authentication and authorization
- Use HTTPS in production
- Sanitize data before displaying to prevent XSS
- Use connection strings with authentication
- Implement proper access controls
- Validate and sanitize all database inputs
- Use MongoDB's built-in security features
- Use strong, random secrets for JWT signing
- Implement proper token expiration
- Store tokens securely (HTTP-only cookies recommended)
- Validate tokens on every protected route
This project includes:
- CodeQL Analysis: Automated code scanning for security vulnerabilities
- Dependency Scanning: Regular checks for vulnerable dependencies
- Security Audits: Automated npm audit checks in CI/CD pipeline
For any security-related questions or concerns, please contact:
- Email: [security@yourproject.com]
- GitHub: [@code-craka]
Thank you for helping keep our project secure!