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

Find unmaintained #4

Closed
wants to merge 3 commits into from
Closed

Find unmaintained #4

wants to merge 3 commits into from

Conversation

Dwood15
Copy link

@Dwood15 Dwood15 commented May 1, 2018

Allow users to search their package.json for old/unmaintained packages as part of an audit subcommand or flag.

Shoutout to @iarna

@zkat
Copy link
Contributor

zkat commented May 2, 2018

I'll drop a comment about potential impact here when considering answers: There's an immense number of packages that haven't been updated in well over a year (or several years), which are still in widespread use -- and they're not bitrotted, but considered stable, and are perfectly usable. I'm concerned about the unnecessary noise something like this might add and I'd like to hear more about mitigations to that. I think folks would be surprised at the number of low-maintenance packages in their trees.

@iarna
Copy link
Contributor

iarna commented May 3, 2018

It might be more appropriate to only list something as unmaintained when there are higher ranked alternatives available. That at least makes the information actionable. We do have a maintenance quality metric currently on the website, fwiw.

@zkat zkat self-requested a review May 9, 2018 21:52
@iarna iarna requested review from a team May 9, 2018 22:28
@nickserv
Copy link

nickserv commented May 28, 2018

I don't think this is necessary given that npm is pretty good at supporting the installation of older packages compared to other package managers. From a tooling perspective, commands like outdated, deprecate, and audit already solve the maintenance and security concerns of using old packages well enough.

@zkat
Copy link
Contributor

zkat commented Jan 31, 2019

Hey! Thanks again for filing this RFC!

We've decided to pass on this particular proposal, based on prior discussion and responses from other users.

So, I'm gonna close this, but I look forward to other ideas coming our way that address these pain points!

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 this pull request may close these issues.

4 participants