mkcert
mkcert copied to clipboard
fix(sec): upgrade golang.org/x/crypto to 0.17.0
What happened?
There are 1 security vulnerabilities found in golang.org/x/crypto v0.0.0-20220331220935-ae2d96664a29
What did I do?
Upgrade golang.org/x/crypto from v0.0.0-20220331220935-ae2d96664a29 to 0.17.0 for vulnerability fix
What did you expect to happen?
Ideally, no insecure libs should be used.
How can we automate the detection of these types of issues?
By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.
The specification of the pull request
PR Specification from OSCS
Ping @FiloSottile