| Version | Supported |
|---|---|
| 0.x.x | ✅ Current |
Please do NOT open a public GitHub issue for security vulnerabilities.
To report a security vulnerability:
- Email: security@secure-ref.dev (or create a private GitHub advisory)
- Include:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Suggested fix (optional)
Response SLA:
- Acknowledgement: within 24 hours
- Fix timeline: within 72 hours for critical, 7 days for high
- Keep
secure-refupdated to the latest version - Run
npm auditregularly in your project - Enable
npm provenanceverification - Never disable security headers without understanding the risk (see
secureRef.reference())
- ✅ Zero runtime dependencies (eliminates supply chain risk)
- ✅
npm auditclean on every release - ✅ 2FA enabled on npm publish account
- ✅ Signed commits (GPG)
- ✅ npm provenance attestation
- ✅ OWASP Top 10:2025 aligned
We follow responsible disclosure. Fixes will be released within the stated SLA, followed by a public advisory post-fix.