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

Lower score in "up-to-date dependencies" if direct dependency is "discontinued" #1445

Closed
sigurdm opened this issue Mar 3, 2025 · 2 comments · Fixed by #1447
Closed

Lower score in "up-to-date dependencies" if direct dependency is "discontinued" #1445

sigurdm opened this issue Mar 3, 2025 · 2 comments · Fixed by #1447

Comments

@sigurdm
Copy link
Contributor

sigurdm commented Mar 3, 2025

Depending on a discontinued package is not healthy for the ecosystem in the long run

It could be seen as equivalent to not allowing the latest version of a dependency in your constraint.

cc @kevmoo @mit-mit

@Rexios80
Copy link
Contributor

Rexios80 commented Mar 3, 2025

I'm not sure about this. It's possible for a package to be marked as "discontinued" and still be fully functional.

@sigurdm
Copy link
Contributor Author

sigurdm commented Mar 3, 2025

I'm not sure about this. It's possible for a package to be marked as "discontinued" and still be fully functional.

(opinions:)

While this is true, it is not healthy in the long run.

Several things are potentially fully functional (such as having false positive warnings, not allowing the latest version of a dependency),

We still want package authors to react to these and move the ecosystem forwards.

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

Successfully merging a pull request may close this issue.

2 participants