Do excellent vulnerability reports

A guide from the curl maintainer on how to write high-quality vulnerability reports to open source projects. Key recommendations include: writing a clear human-authored intro paragraph explaining the problem, providing a standalone reproducer, submitting a patch if possible, specifying affected versions, following the project's preferred submission channel, and remaining available for collaboration throughout the process. The guide also covers how security advisories are written and emphasizes respecting the limited bandwidth of volunteer maintainers.