Current best practice for a "retirement" project on github and npmjs.org?

Question

I support the public github project (and npm). When I created the project, it solved my specific requirements better than the alternatives available. However, the community caught up with my decision and exceeded it. I do not even use the tool that I created, and I am not interested in saving it. I updated README, but I still get requests for it. Should I just take it off? Is it considered rude if others try to develop it and try to contribute? So far, I have not been able to get these others to take responsibility as my companion.

I am not looking for arbitrary subjective opinions, but rather evidence of some kind of consensus - perhaps in the form of documentation or guidance from a recognized authority. Thank.

Answer 1

• Modify README.mdand post a large, brilliant disclaimer saying “this is no longer supported, please consider using XXX instead”
• Use npm deprecateto post an obsolescence notification on every installation.

Is it considered rude if others try to develop it and try to contribute?

Yes.