mirror of
https://github.com/super-linter/super-linter.git
synced 2024-11-30 04:30:59 -05:00
d465382ed5
* Update documentation * Fix typos * Update security policy * Remove outdated instructions * Fix list * Add more info to config load step * Don't test linter.yml * Point to the cd workflow in README * Move badge up * Add info about Make help --------- Co-authored-by: Zack Koppert <zkoppert@github.com>
17 lines
785 B
Markdown
17 lines
785 B
Markdown
# Reporting Security Issues
|
|
|
|
The super-linter team and community take security bugs seriously. We appreciate
|
|
your efforts to responsibly disclose your findings, and will make every effort
|
|
to acknowledge your contributions.
|
|
|
|
To report a security issue, please use the GitHub Security Advisory
|
|
["Report a Vulnerability"](https://github.com/super-linter/super-linter/security/advisories/new)
|
|
feature.
|
|
|
|
The super-linter team will send a response indicating the next steps in handling
|
|
your report. After the initial reply to your report, the security team will keep
|
|
you informed of the progress towards a fix and full announcement, and may ask
|
|
for additional information or guidance.
|
|
|
|
Report security bugs in third-party software to the person or team maintaining
|
|
the third-party software.
|