fix(sec): upgrade jsonwebtoken to 9.0.0
What happened?
There are 1 security vulnerabilities found in jsonwebtoken 8.5.1
What did I do?
Upgrade jsonwebtoken from 8.5.1 to 9.0.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
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.
Superseded by #1753 with regression tests passing
Superseded.