Self-hosted project management for devs and their clients: tickets, time tracking, docs and meetings, with an AI assistant that cites its sources. AGPL-3.0.
Security Policy
We take the security of Lalabase seriously. Because Lalabase is built for teams that care about data sovereignty and self-hosting, a vulnerability can directly affect the confidentiality of our users' data. Thank you for helping keep the project and its users safe.
Supported Versions
Lalabase is under active development. Security fixes are provided for:
| Version | Supported |
|---|---|
| Latest tagged release | ✅ |
| Older releases | ❌ (please upgrade) |
If you self-host, always run the latest tagged release to receive security fixes.
Reporting a Vulnerability
Please do not report security vulnerabilities through public GitHub issues, pull requests, or discussions.
Instead, report them privately by email to:
If you prefer, you may also use GitHub's private vulnerability reporting ("Report a vulnerability" under the repository's Security tab).
To help us triage quickly, please include where you can:
- A description of the vulnerability and its potential impact
- Steps to reproduce (proof-of-concept, affected endpoint/component, request samples)
- The affected version, commit, or deployment type (Cloud vs. self-hosted)
- Any suggested mitigation, if you have one
What to Expect
- Acknowledgement within 3 business days of your report.
- An initial assessment and severity classification within 10 business days.
- We will keep you informed about remediation progress and coordinate a disclosure timeline with you.
- With your consent, we are happy to credit you once a fix is released.
Disclosure Policy
We follow coordinated disclosure. Please give us a reasonable opportunity to remediate before any public disclosure — ordinarily up to 90 days from your report, or sooner once a fix has shipped. (This 90-day disclosure window is separate from the response times above, which describe how quickly we get back to you.)
To the extent permitted by applicable law, we will not initiate or support legal action against security researchers who:
- Act in good faith and avoid privacy violations, data destruction, and the disruption or degradation of our services,
- Only access, modify, or interact with data or accounts they own or have explicit permission to test, and
- Give us the disclosure window above to remediate before going public.
This policy is the authorization boundary for security testing of Lalabase: it does not authorize actions against third-party services, infrastructure, or data we do not control, and it does not waive any rights of third parties.
Thank you for contributing to the security of Lalabase.