-
Notifications
You must be signed in to change notification settings - Fork 42
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
Is this project alive? #44
Comments
Hi @israelroldan! A while back I sort of accepted to do some maintenance because I needed this project to live on but @christkv was very busy with other stuff (and still is). He gave me merging rights, and I have mainly reviewed a few pull requests (mostly by running tests myself to verify that nothing breaks) but I'm willing to pass the keys on to you if you're motivated about taking this project forward. The biggest problem I had (and still have) was not being able to do new releases. I believe I've pinged Chris a few times about this (to ask for either a spot release or the rights to release myself) but I haven't heard back yet. |
That's more me loosing track of it due to being busy with work and kids. I'm happy to add you as a collaborator @israelroldan if you want to take charge of the module. Also I think there is a way of making more people than me be able to publish. Just need to figure out how to do it with npm. Feel free to pass me your npm user names by mail to christkv at mongodb com and I'll try to get them added. @israelroldan let me know if you want to be added as a collaborator. |
Soo...this issue is now 7 years ago... does anything changed. IN npm i see there was no update for 11 years. and this is just moderate because i forced it to use mime 2.0.3 with npm-force-resolutions ... otherwise also mime make a highly severe vulnerability. Here should happen something. Git is something what you can't just leave out and uninstall it if you have vulnerabilities. Its needed for million of project. So if you have no coworkers for the project.. Search for them... |
First of all, thanks @christkv for starting it and providing us node users with basic access to the git api.
Given that the last release was published 4 years ago and the last commits were more than 2 years ago... I was wondering if there was any roadmap to continue its development moving forward.
If you're looking for someone to take on it, let me know, I'll be very happy to help and coordinate the effort!
Gracias!
The text was updated successfully, but these errors were encountered: