You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1 vulnerability reported
0 vulnerabilities ignored
+==============================================================================+
VULNERABILITIES FOUND
+==============================================================================+
-> Vulnerability found in jinja2 version 3.1.4
Vulnerability ID: 70612
The same issue is seen if the following command is used pdm export -f requirements --without-hashes | safety check --ignore 70612 --stdin
Describe the ideal solution
Safety should ignore the warnings specified on commandline.
Alternatives and current workarounds
None.
Additional context
NA
What I Did
Ran Github CI.
The text was updated successfully, but these errors were encountered:
We appreciate your effort in reporting this. Our team will review it and get back to you soon.
If you have any additional details or updates, feel free to add them to this issue.
Note: If this is a serious security issue that could impact the security of Safety CLI users, please email [email protected] immediately.
Thank you for reporting this issue. The "check" command has been deprecated and is no longer supported. However, we now offer the "scan" command, which includes this functionality. You can sign up for our beta program at https://platform.safetycli.com/ to learn more!
Checklist
Safety version
3.2.8
Python version
3.10.12
Operating System
Linux Ubuntu.
Describe the problem you'd like to have solved
Check https://github.com/dyumnin/cocotb-ralgen/actions/runs/11438139741/job/31819128744
Safety is executed as follows
pdm export -f requirements --without-hashes | pdm run safety check --ignore 70612 --stdin
The Jinja Warning is still issues
The same issue is seen if the following command is used
pdm export -f requirements --without-hashes | safety check --ignore 70612 --stdin
Describe the ideal solution
Safety should ignore the warnings specified on commandline.
Alternatives and current workarounds
None.
Additional context
NA
What I Did
Ran Github CI.
The text was updated successfully, but these errors were encountered: