Reporting issues in Weblate¶
Weblate issue tracker is hosted at GitHub.
Feel welcome to report any issues you have or suggest improvements for Weblate there. There are various templates prepared to comfortably guide you through the issue report.
If what you have found is a security issue in Weblate, please consult the Reporting security issues section below.
If you are not sure about your bug report or feature request, you can try Weblate discussions.
Reporting security issues¶
Weblate’s development team is strongly committed to responsible reporting and disclosure of security-related issues. We have adopted and follow policies that are geared toward delivering timely security updates to Weblate.
Most normal bugs in Weblate are reported to our public GitHub issues tracker, but due to the sensitive nature of security issues, we ask that they not be publicly reported in this fashion.
Instead, if you believe you’ve found something in Weblate that has security implications, please submit a description of the issue to security@weblate.org, GitHub, or using HackerOne.
A member of the security team will respond to you within 48 hours, and depending on what action is taken, you may get more follow-up emails.
Note
Sending encrypted reports
If you want to send an encrypted email (optional), please use the public
key for michal@weblate.org with ID 3CB 1DF1 EF12 CF2A C0EE 5A32 9C27 B313
42B7 511D. This public key is available on the most commonly used key servers,
and from Keybase.
Hint
Weblate depends on third-party components for many things. In case you find a vulnerability affecting one of those components in general, please report it directly to the respective project.
Some of these are: