-
Notifications
You must be signed in to change notification settings - Fork 33
Is this project still alive - unfixed critical vulnerabilities in dependencies #60
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
Comments
This comment was marked as resolved.
This comment was marked as resolved.
@MikeMcC399, I was granted write access back in the day. ✍️ |
As discussed elsewhere, the last release was https://github.com/indexzero/ps-tree/releases/tag/1.2.0 in Nov 2018, so the answer is effectively that the project is no longer maintained if it does not have the ability to trigger new releases. See also the npm registry version list https://www.npmjs.com/package/ps-tree?activeTab=versions |
This project is not dead. It's simply that – as John Lennon would say – "Open Source is what happens when you're busy making other plans." Contributions are always welcome, but please forgive delays in my response. I started this project when I was single. I now have three kids. I get many emails for Github issues which makes it hard to parse out the signal from the noise. Recently, I created a new email address for |
Welcome back!
|
Running
npm audit
lists many vulnerabilities:Since there are pull requests still open fixing some of these issues dating from 2022, it seems that this project is abandoned.
@indexzero : is it worth creating a fix for these issues? I would do this, only if we have a chance to get this project up to date on npmjs too.
The text was updated successfully, but these errors were encountered: