-
Notifications
You must be signed in to change notification settings - Fork 0
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
Distinguishing between dead and stable packages #5
Comments
One factor could be looking at usage of the package — whether it's growing or declining. If it looks inactive, but new users are still adopting it, then it's probably stable. If it's inactive and loses users, then it's dead. A simpler solution may be to have slightly different ranking for crates named *-sys and with versions past 1.0. |
Note that I'm aware of this caveat. It's mentioned in the README:
Detecting this with non-reliable magic is a no-no for me. Instead, I think users should be conscious |
There are some kinds of packages that don't require active maintenance:
very small single-purpose packages that can be finished
*-sys packages/FFI bindings. They may not need to change at all, or may only require updating once in a while when the API of the underlying library/system changes.
Mature projects that don't have much churn, because they're stable and maintain high degree of backwards compatibility (although Rust probably doesn't have these yet :)
Related to #3
The text was updated successfully, but these errors were encountered: