|
| 1 | +--- |
| 2 | +title: Questions, bugs, feedback |
| 3 | +linkTitle: Feedback |
| 4 | +description: How to interact with the DHI team |
| 5 | +keywords: software supply chain security, feedback, bugs, discussion, questions |
| 6 | +weight: 21 |
| 7 | +--- |
| 8 | + |
| 9 | +We’re committed to maintaining the quality, security, and reliability of the Docker Hardened Images (DHI). |
| 10 | +As part of that commitment, we encourage the community to collaborate with us in improving the Hardened Images ecosystem. |
| 11 | + |
| 12 | +## Questions or discussions |
| 13 | + |
| 14 | +You can use the [GitHub Discussions board](https://github.com/docker-hardened-images/discussion) to engage with the DHI |
| 15 | +team for |
| 16 | + |
| 17 | +- General questions about DHIs |
| 18 | +- Best practices and recommendations |
| 19 | +- Security tips and advice |
| 20 | +- Show and tell your implementations |
| 21 | +- Community announcements |
| 22 | + |
| 23 | +## Reporting Bugs or Issues |
| 24 | + |
| 25 | +You can [open a new issue](https://github.com/docker-hardened-images/discussion/issues/) for topics such as |
| 26 | + |
| 27 | +- Bug reports |
| 28 | +- Feature requests |
| 29 | +- Documentation improvements |
| 30 | +- Security vulnerabilities (see security policy) |
| 31 | + |
| 32 | +We encourage to first search existing issues to see if it’s already been reported. |
| 33 | +Our team reviews reports regularly and appreciates clear, actionable feedback. |
| 34 | + |
| 35 | +## Responsible Security Disclosure |
| 36 | + |
| 37 | +It is forbidden to post details of vulnerabilities before coordinated disclosure and resolution. |
| 38 | + |
| 39 | +If you discover a security vulnerability, please report it responsibly by following Docker’s [security disclosure](https://www.docker.com/trust/vulnerability-disclosure-policy/). |
| 40 | + |
0 commit comments