To be fair, last update isn’t the end all be all. If the project is in a stable place, and there haven’t been any breaking changes, there’s just no need to update.
On the one hand, sure. On the other hand, if there hasn’t been even a tiny bug fix or feature update in that long it calls into question (at least for me) whether when there is inevitably a breaking change, security issue with a library, whatever - that it will be addressed. If I don’t have some level of confidence in that, I’d rather not rely on the tool.
This kind of concern could be handled by contacting the developer or engaging with the community around the tool to see what the project status is, and why it isn’t being updated.
To be fair, last update isn’t the end all be all. If the project is in a stable place, and there haven’t been any breaking changes, there’s just no need to update.
On the one hand, sure. On the other hand, if there hasn’t been even a tiny bug fix or feature update in that long it calls into question (at least for me) whether when there is inevitably a breaking change, security issue with a library, whatever - that it will be addressed. If I don’t have some level of confidence in that, I’d rather not rely on the tool.
This kind of concern could be handled by contacting the developer or engaging with the community around the tool to see what the project status is, and why it isn’t being updated.