| Version | Supported |
|---|---|
| latest | ✅ |
| < latest | ❌ |
We recommend always using the latest release for security updates.
We take the security of this project seriously. If you discover a security vulnerability, please follow these steps:
Do not open a public issue. Instead, report vulnerabilities using one of these methods:
-
GitHub Private Vulnerability Reporting (preferred):
- Go to the Security tab
- Click "Report a vulnerability"
- Provide details about the vulnerability
-
Email: Send an email to isberg.peter+cl@gmail.com with:
- Description of the vulnerability
- Steps to reproduce
- Potential impact
- Any suggested fixes (if applicable)
- Acknowledgment: We will acknowledge receipt of your report within 48 hours
- Investigation: We will investigate the report and confirm the vulnerability
- Timeline: We aim to resolve critical vulnerabilities within 7 days
- Communication: We will keep you informed of our progress throughout the process
- Credit: We will credit you in the security advisory (unless you prefer to remain anonymous)
Once a vulnerability is fixed, we will:
- Publish a security advisory on GitHub
- Release a patched version
- Notify users via release notes
This project follows these security practices:
- Dependency Management: Automated dependency updates via Dependabot
- Code Review: All changes require review before merging
- CI/CD Security: GitHub Actions workflows use pinned dependencies and minimal permissions
- Static Analysis: CodeQL runs on every push and PR
- SBOM: Software Bill of Materials generated for transparency
- Maintainer: Peter Isberg
- Email: isberg.peter+cl@gmail.com