Create SECURITY.md #2147
Comments
|
@JamieSlome Hey! Thanks for reporting. Please refer to helmfile/helmfile#135 (Also note that we've moved to |
mumoshu
added a commit
to helmfile/helmfile
that referenced
this issue
Jun 5, 2022
Probably this is the best we can currently offer. Any suggestions are welcomed though. Ref roboll/helmfile#2147 Signed-off-by: Yusuke Kuoka <[email protected]>
mumoshu
added a commit
to helmfile/helmfile
that referenced
this issue
Jun 5, 2022
Probably this is the best we can currently offer. Any suggestions are welcomed though. Ref roboll/helmfile#2147 Signed-off-by: Yusuke Kuoka <[email protected]>
|
@mumoshu - thanks for your response and diligence 👍 @arshadkazmi42 - are you able to re-submit your report against |
|
@JamieSlome I have verified, the issue does not exists in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@arshadkazmi42) has found a potential issue, which I would be eager to share with you.
Could you add a
SECURITY.mdfile with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.Looking forward to hearing from you 👍
(cc @huntr-helper)
The text was updated successfully, but these errors were encountered: