| Version | Supported |
|---|---|
| 0.9.x | ✅ |
| < 0.9 | ❌ |
We take security seriously. If you discover a vulnerability in Docs Assembler, please report it privately so we can address it before public disclosure.
Please do NOT open a public issue for security vulnerabilities.
Email us directly at team@netoftrees.com with:
- A clear description of the vulnerability
- Steps to reproduce (if applicable)
- Potential impact assessment
- Any suggested mitigation (optional)
- Acknowledgement within 48 hours
- Initial assessment within 5 business days
- Resolution timeline communicated once assessed
- Credit in release notes if you wish to be named (with your permission)
This policy covers:
- The Docs Assembler VS Code extension
- The template repository and build pipeline
- Published documentation output (Markdown/HTML generation)
It does not cover:
- Third-party display tools implementing the Display Tool Contract
- Content authored by users of the extension
- GitHub Pages or other hosting platforms
If you are building a display tool that consumes Docs Assembler output, please review the Display Tool Contract security section, which covers:
- Proxy allowlist validation for cross-origin fragment loading
- Path validation for proxied assets
- Rate limiting and abuse prevention
- Content-Type preservation for proxied media
We follow a coordinated disclosure approach:
- We work with reporters to validate and fix the issue
- We release a patched version
- We publish an advisory after users have had reasonable time to update
We aim to complete this cycle within 90 days of initial report, though critical vulnerabilities may be expedited.