-
Notifications
You must be signed in to change notification settings - Fork 406
Description
I was recently complaining on how core ecosystem crates like term are unmaintained. Someone responded with an interesting idea: have RustSec track this information and expose it through cargo-audit.
Here is a broad strokes sketch of how I think this could work:
- Define a policy for what counts as an "unmaintained crate" (see below)
- In this repo, create a
crates/<unmaintained_crate>/unmaintained.tomlfile containing information about the crate's current status. - Surface this information as a warning in
cargo-auditwith an option to make it an error.
What policy makes sense for an unmaintained.toml? Well, the term crate is pretty clear-cut, the maintainer posted a "Looking For Maintainer (LFM)" GitHub issue:
I think a good starting point for a policy is, unlike other RustSec advisories, having package maintainers self-file these to announce to the community that the crate is unmaintained. I think this could have a secondary effect of helping maintainers in this position to find new maintainers. New maintainers can then remove the unmaintained.toml once they take ownership, and by doing so, the RustSec database gets a bonus added effect of becoming a sort of visibility point / audit log of crate ownership transfer in these cases.