Open realize096 opened 9 months ago
There are 1 security vulnerabilities found in Django 3.2.9
Upgrade Django from 3.2.9 to 4.0.6 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
What happened？
There are 1 security vulnerabilities found in Django 3.2.9
What did I do？
Upgrade Django from 3.2.9 to 4.0.6 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