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.
El equipo de desarrollo de Weblate está firmemente comprometido con la divulgación y los informes responsables de problemas relacionados con la seguridad. Hemos adoptado y seguimos políticas orientadas a entregar actualizaciones de seguridad a Weblate de manera oportuna.
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.
Nota
Sending encrypted reports
Si desea enviar un correo electrónico cifrado (opcional), utilice la clave pública de michal@weblate.org con ID 3CB1DF1EF12CF2AC0EE5A329C27B31342B7511D. Esta clave pública está disponible en los servidores de claves más utilizados y en Keybase.
Consejo
Weblate depende de componentes de terceros para muchas cosas. En caso de que encuentre una vulnerabilidad que afecte a uno de esos componentes en general, infórmelo directamente al proyecto correspondiente .