Dependency Scanning
npm audit
npm audit is executed as part of the CI pipeline on every pull request and on a scheduled basis against the production branch. It checks all direct and transitive dependencies against the npm advisory database.
Dependabot / Automated Updates
Automated dependency update pull requests are configured to:- Open PRs for security patches automatically
- Group minor/patch updates to reduce PR noise
- Require CI passage before any dependency update is merged
Runtime Dependency Inventory
Key dependencies and their security posture:Vulnerability Severity SLAs
Application-Layer Security Testing
Beyond dependency scanning, security is verified at the application layer:- Security regression tests (
src/tests/api/security.test.ts) run in CI on every PR - Tests verify that API routes do not expose connection strings, stack traces, or environment variable names in error responses
- New API routes require a corresponding security review checklist item in the PR template
Infrastructure Scanning
Disclosure and Patch Process
- Vulnerability discovered (automated scan, researcher report, or vendor advisory)
- Severity assessed against CVSS and business context
- Patch or mitigation implemented on a feature branch
- CI pipeline + security test suite run
- Deployed to preview environment for validation
- Merged to
mainand deployed to production - Audit log entry or incident ticket created documenting the remediation