Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the community to "self-monitor" the maintenance status #69

Open
CommanderStorm opened this issue Apr 17, 2024 · 1 comment
Open

Comments

@CommanderStorm
Copy link

Hi,
I wanted to ask if something as discussed in rust-secure-code/wg#44 might be possibe or entirely out of scope:

Some sort of automation for determining the health of particular crates might be helpful in terms of determining what crates to mark as unmaintained, particularly one that emphasizes crates with large numbers of downloads or downstream dependencies. In general it'd be nice to have some sort of platform for doing analysis of the entire crates.io ecosystem.

Reason why this might be in scope:

  • it would be really helpfull to be able to focus effort where it is needed most "where people are drowning/burning out"

Reason why this might be out of scope:

  • The "maintenance status" might not be resolvable from just the crates info
@szabgab
Copy link
Owner

szabgab commented Apr 17, 2024

If I understand it correctly then it is definitely in scope for the Rust Digger. We are collecting information both from Crates.io and from the repositories of the projects.

So we could have some combination of
"importance":

  • number of downloads
  • number of direct dependencies
  • number of total dependencies.
  • etc..

and "activity":

  • number of open issues
  • number of PRs
  • most recent commit
  • number of committers
  • "bus factor"
  • etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants