-
-
Notifications
You must be signed in to change notification settings - Fork 40
Add support for --ignore #223
Comments
I think this PR should be of help for you #221 . |
This would be helpful given the state of https://rustsec.org/advisories/RUSTSEC-2020-0071 and chronotope/chrono#602 The CVE is low risk for chrono and the problematic dependency should be removed in the next version. |
From @djmitche in #221 (comment)
So we could probably close this issue. Though explicit documentation might be more helpful than this github issue for future users. |
Yeah, this seems to be the closest there is to documentation of At any rate, this support is now added so this issue can be closed. |
Nice! I opened rustsec/rustsec#650 to capture documentation that I think might help. |
heh, though based on GothenburgBitFactory/taskwarrior#2903 (comment) @pinkforest might be in favor of re-opening this issue. :) |
Do the checklist before filing an issue:
actions-rs
Actions?Motivation
Sometimes addressing an advisory is not important for a repository. Maybe it's only used in test or deprecated code, or is a difficult fix and analysis of the vulnerability shows the repo isn't actually vulnerable. In those cases,
cargo audit
provides--ignore
, but it seems this option is not available in the GitHub action.Workflow example
The text was updated successfully, but these errors were encountered: