WarblerJS treats security as an architecture boundary, not a post-release add-on.
| Version | Support status |
|---|---|
0.6.x |
Supported |
< 0.6 |
Unsupported |
Warbler is currently in the pre-1.0 release series. Security fixes are provided for the latest published minor release.
Do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
Report vulnerabilities through GitHub Private Vulnerability Reporting in the repository's Security tab.
Private Vulnerability Reporting must be enabled before this repository is made public. Until it is enabled, public publication remains blocked.
Include:
- The affected Warbler version and package.
- A clear description of the vulnerability.
- Minimal reproduction steps.
- The security impact.
- Any known mitigation.
Do not include unrelated secrets, credentials, private keys, customer data, or production data.
- Acknowledge the report through the approved private channel.
- Classify affected packages and supported release lines.
- Reproduce without retaining secrets or production data.
- Prepare the smallest compatible fix.
- Add permanent regression coverage.
- Run the affected test suites and release checks that exist for the change.
- Prepare advisory, changelog, and release notes.
- Publish the patch according to the supported release line.
Security review covers:
- Compiler analysis and generated bindings.
- Runtime lifecycle and dependency-injection scopes.
- HTTP parsing, limits, security headers, CSRF, cookies, redirects, static assets, streaming, and error responses.
- Database query safety, transactions, migrations, row locking, and soft deletes.
- WebSocket validation and lifecycle.
- Package publication and supply-chain boundaries.
- Public Web Standard API portability.
Security fixes must include permanent regression coverage.