Feature/ci security and performance

[millicentogalanya]

Description

Enhanced the CI/CD pipeline by adding linting, security auditing, and performance benchmarking stages. These checks improve code quality, detect vulnerabilities early, and provide faster feedback during development.

Type of Change

• 🐛 Bug fix (non-breaking change that fixes an issue)
• ✨ New feature (non-breaking change that adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🔧 Code refactor (no functional changes)
• 📚 Documentation update
• 🧪 Tests (adding or updating tests)
• 🔒 Security (security-related changes)
• 🚀 Performance (performance-related changes)
• 🎨 UI/UX (user interface changes)
• 🛠️ DevOps (deployment, CI/CD, infrastructure changes)

Changes Made

Code Changes

• Added automated lint checks to the CI pipeline.
• Integrated dependency and security vulnerability auditing.
• Added performance benchmark execution and optimized dependency caching to reduce CI runtime.

Documentation Updates

Database/Schema Changes

Testing

Manual Testing

Automated Tests

• Unit tests pass
• Integration tests pass
• E2E tests pass (if applicable)
• Performance tests pass (if applicable)

Test Coverage

Screenshots/Videos (UI Changes)

Before	After

Breaking Changes

Checklist

Code Quality

• Code follows project style guidelines
• Code is self-documenting or properly commented
• No console.log statements or debugger breakpoints left
• No unused imports or variables
• Code passes linting checks

Testing

• Unit tests added/updated for new functionality
• Integration tests added/updated if needed
• Manual testing completed
• Edge cases considered and tested
• Tests pass locally

Documentation

• README updated if needed
• API documentation updated if needed
• Inline code documentation added/updated
• Comments added for complex logic

Security

• Security implications reviewed
• No sensitive data exposed
• Input validation added where needed
• Authentication/authorization considered

Performance

• Performance impact assessed
• No performance regressions introduced
• Bundle size checked (frontend)
• Database queries optimized (backend)

Deployment

• Environment variables documented
• Database migrations included
• Backward compatibility maintained
• Rollback plan considered

Legal/Compliance

• DCO (Developer Certificate of Origin) signed
• License headers added to new files
• x ] Third-party dependencies reviewed
• GDPR/privacy implications considered

Related Issues

Closes #471

Additional Context

[vercel]

@millicentogalanya is attempting to deploy a commit to the Ebeleokolo's projects Team on Vercel.

A member of the Team first needs to authorize it.