-
Notifications
You must be signed in to change notification settings - Fork 49
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
Maintener(s) wanted #80
Comments
I'm happy to take this on. Please contact me at |
I would like to help out. |
@andrewzey : I've added you on npmjs as maintener. |
added @andrewzey |
np, good luck ! |
Hi Team. Unfortunately I won't be able to maintain this, and we'll need the repo owner to choose a new maintainer. I no longer am using Restify - I'm using Express instead for my projects, as it's better supported by most third party integrations, and in practice not any slower than Restify since the framework overhead makes up for a tiny fraction of every request, and the performance difference is unmeasurable in production environments. |
@gchauvet @z0mt3c I've been using Restify as the core for our Node.js training classes and have been bothered with the lack of clean, up-to-date, no-vuln-bearing request validator solution ever since. This package is the best of the two options for that, but it carries 3 vulns due to outdated Lodash, is incompatible with Restify 6+ due to its new router's route management, etc. I can absolutely take this over, and address a number of the outstanding issues to boot. This could be done in a matter of weeks. Would you be willing to add me on GitHub and npm so I can help move this forward? |
I'm busy for a long while, then I can't assume the maintenance of this project.
Moreover, I don't work anymore with node js technology.
If someone want to take lead on this project, contact me.
The text was updated successfully, but these errors were encountered: