It's actually not at all about time. @apple does come with some obvious legal implications, but even if that weren't the case, I have zero passion in this project, because I don't think I should have ever created it in the first place. Quite honestly, I don't think anyone should be using it, as the things that people tend to want to fix are related to indentation and whitespace, which can only truly (and safely) be done by something AST-aware like Prettier.

I was perhaps a bit too confident that I could solve the indentation problem w/o AST, but I'm entirely convinced now that that is not remotely possible w/o machine learning or something crazy like that.

I'm definitely surprised at the popularity of this package, but my advice would be to take a step back and reevaluate why you're using it in the first place. Perhaps you'll realize, like me, that there is a better way to do it.

Please, just use Prettier in 2020. I haven't used this tool in many years and I don't plan on ever using it again.

Thanks for the fast and clear answer @jedmao ! I agree, there are other options such as Prettier or editorconfig-checker that people can use. I've just seen a lot of people still using eclint and getting a clear answer on the future of eclint was my goal here. I keep that issue open so people are able to recognize that eclint is no longer maintained. Might be worth to add a note to the README.md and to archive to project here to make it clear for everybody.

https://docs.github.com/en/free-pro-team@latest/github/creating-cloning-and-archiving-repositories/archiving-repositories

Easier for peopling dropping by and then immediately see that this repo is unmaintained. Leaving it here for your consideration. 👍🏻