-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add a security policy to inform users where to report security issues, and to make the OpenSSF scorecard slightly happier; https://securityscorecards.dev/viewer/?uri=github.com/docker/compose Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
- Loading branch information
Showing
1 changed file
with
44 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,44 @@ | ||
# Security Policy | ||
|
||
The maintainers of Docker Compose take security seriously. If you discover | ||
a security issue, please bring it to their attention right away! | ||
|
||
## Reporting a Vulnerability | ||
|
||
Please **DO NOT** file a public issue, instead send your report privately | ||
to [security@docker.com](mailto:security@docker.com). | ||
|
||
Reporter(s) can expect a response within 72 hours, acknowledging the issue was | ||
received. | ||
|
||
## Review Process | ||
|
||
After receiving the report, an initial triage and technical analysis is | ||
performed to confirm the report and determine its scope. We may request | ||
additional information in this stage of the process. | ||
|
||
Once a reviewer has confirmed the relevance of the report, a draft security | ||
advisory will be created on GitHub. The draft advisory will be used to discuss | ||
the issue with maintainers, the reporter(s), and where applicable, other | ||
affected parties under embargo. | ||
|
||
If the vulnerability is accepted, a timeline for developing a patch, public | ||
disclosure, and patch release will be determined. If there is an embargo period | ||
on public disclosure before the patch release, the reporter(s) are expected to | ||
participate in the discussion of the timeline and abide by agreed upon dates | ||
for public disclosure. | ||
|
||
## Accreditation | ||
|
||
Security reports are greatly appreciated and we will publicly thank you, | ||
although we will keep your name confidential if you request it. We also like to | ||
send gifts - if you're into swag, make sure to let us know. We do not currently | ||
offer a paid security bounty program at this time. | ||
|
||
## Supported Versions | ||
|
||
This project docs not provide long-term supported versions, and only the current | ||
release and `main` branch are actively maintained. Docker Compose v1, and the | ||
corresponding [v1 branch](https://github.com/docker/compose/tree/v1) reached | ||
EOL and are no longer supported. | ||
|