We commit to publishing security updates for the version of all gowebly projects currently on the main branch.

To report a vulnerability, please e-mail [email protected] with a description of the issue, the steps you took to create the issue, affected versions, and if known, mitigation for the issue.

We should reply within five working days, probably much sooner.

Unfortunately, we do receive spam at this address, as well as well-meaning but ultimately misguided reports that do not represent issues for which this process is appropriate.

We use GitHub's security advisory feature to track open security issues. You should expect a close collaboration as we work to resolve the issue you have reported. Please reach out to [email protected] again if you do not receive prompt attention and regular updates.

This section describes the process used by the gowebly project team when handling vulnerability reports.

Vulnerability reports are received via the [email protected] e-mail alias. Certain team members who have been designated the "vulnerability management team" receive these e-mails. When receiving such an e-mail, they will:

1. Reply to the e-mail acknowledging its receipt, cc'ing [email protected] so that the other members of the team are aware that they are handling the issue. If the e-mail does not describe an actual vulnerability, the process will stop here.
2. Create a new security advisory for gowebly project. One must be one of the repo admins to do this. Vulnerability management team members who are not also a repo admin will reach out to the repo admins until they find one who can create the advisory. The repository administrator, who is also a member of the vulnerability management team, is @koddr.
3. Add the reporter to the security advisory so that they can get updates.
4. Inform the relevant team lead, adding them to the security advisory.

As the fix is being developed, they will then reach out to the reporter to ask them if they would like to be involved and whether they would like to be credited. For credit, the GitHub security advisory UI has a field that allows contributors to be credited.

When the issue is resolved, they will contact the release team and our PR team to coordinate the publication of the security advisory.

Security issues have the priority level. We attempt to fix them as quickly as possible.

For more information on security advisories, see the GitHub documentation.