rustsec / rustsec/advisory-db

There should be a way to indicate how long a crate has been unmaintained

Open
#2,233 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
1.2k
Forks
544
Avg merge
1d 10h
Merged PRs (30d)
45

Description

Most of the "$crate has been unmaintained" advisories are for crates that have sat around for a while without any clear indication of maintenance and then after months somebody gets around to asking the maintainer if they've stopped maintaining the thing.

But in some circumstances perhaps there isn't a long period of lack of maintenance, but where the maintainer feels a responsibility to help people understand that some period of inactivity is to be expected. And, maybe indefinitely so. Right now there is not a good way for the maintainer to broadcast this in a timely and effective way without tripping people's CI "supply chain integrity" jobs.

Probably there should be a way to configure "supply chain integrity" tools so that, if a crate has been "unmaintained" for less than X days, then CI shouldn't break. After all, somebody might pick up maintenance of it again quickly. But, apparently it is unclear from reading the metadata how a tool would calculate the approximation of the value of X; there need to be at least two dates to subtract from each other, but there's only one.

I realize this is a tricky issue and I'm not really planning to participate in designing a solution. However, this came up in discussions with some open source maintainers about why it difficult for them to send in an "unmaintained" advisory for their projects; they don't want to break people's CIs. And I think for important non-technical reasons it is something worth addressing.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing how unmaintained advisories and crate metadata are represented, then examine how supply-chain integrity tools could derive or configure an inactivity period; done would be an agreed design for communicating expected inactivity without unnecessarily breaking CI.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.