Open pinkforest opened 2 years ago
This might be a better question to post at https://github.com/RustSec as it's specifically RustSec-related.
I think it might make sense to fork the action under that org so @RustSec can manage maintenance.
Somewhat related issue here: https://github.com/rustsec/rustsec/issues/303
I asked @Shnatsel about it yesterday and was supportive as well to under rustsec org
Folk are using this and seems the maintainer @svartalf seems MIA
There seems to be at least one fork already by @djmitche / GothernburgBitFactory: https://github.com/actions-rs/audit-check/pull/221#issuecomment-1193138925 https://github.com/GothenburgBitFactory/taskwarrior/issues/2830#issuecomment-1179835614
Here: https://github.com/GothenburgBitFactory/audit-check Addressing: https://github.com/actions-rs/audit-check/issues/223
Would it be worthwhile to maintain a fork under GH org until the original maintainer is back
Or maybe we can just add the fork here: https://github.com/rust-secure-code/projects
In most basic form without any actions alternative always might be something like this - but it's pain to maintain vs action-ref:
There is ofc cargo-deny GH action too: https://github.com/EmbarkStudios/cargo-deny-action