advisory-db
advisory-db copied to clipboard
Update reported issues in multiple packages
Sorry for sending PRs for several times. I finally find out how to check all the failed lints together.
Looks like quite a few of these are unfixed with no response from maintainers. Can someone remind me what our usual policy for those cases is?
Last time we have settled on https://github.com/rustsec/advisory-db/issues/1092#issuecomment-954024803
So it requires advance notice and a grace period for the maintainers to be able to take action before the advisory goes live.
For the crate zub, we have got response that it is unmaintained for a while(https://github.com/nilq/zub-vm/issues/14#issuecomment-1717773763). I think the code will not be patched.
Hi, @alex @Shnatsel . Is there any update for this PR?
hi @alex , I am wondering the progress of this PR so far. If the PR has some wrong format then it should be rejected so that I can correct the issues:)