This policy covers every repository in the awesome-humans organisation, and the website, awesome-humans.net. Only the main branch and the deployed website are supported.
- A vulnerability in a workflow, script, or the deployment, such as a way to run code in CI with access to secrets, to change
mainwithout review, or to change what awesome-humans.net serves. - Guidance that makes the projects following it insecure, when describing it in public first would put those projects at risk. An opinion or template that recommends a weak default, or a skill that would apply one, counts.
Report outdated guidance with an already-public fix, such as a package version with a published advisory, as an ordinary issue or pull request.
Use GitHub's private vulnerability reporting: open the affected repository's Security tab and select Report a vulnerability. If that isn't available, email contact@awesome-humans.net.
Don't open a public issue, pull request, or discussion about it.
The maintainer replies in the advisory, and fixes the problem there or in a private fork. Once the fix is merged and deployed, the advisory is published, crediting you unless you ask not to be named.