Closed chncaption closed 8 months ago
There are 1 security vulnerabilities found in com.google.guava:guava 31.1-jre
Upgrade com.google.guava:guava from 31.1-jre to 32.0.0-jre for vulnerability fix
Ideally, no insecure libs should be used.
By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.
PR Specification from OSCS
Kudos, SonarCloud Quality Gate passed!
0 Bugs 0 Vulnerabilities 0 Security Hotspots 0 Code Smells
No Coverage information 0.0% Duplication
What happened?
There are 1 security vulnerabilities found in com.google.guava:guava 31.1-jre
What did I do?
Upgrade com.google.guava:guava from 31.1-jre to 32.0.0-jre 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