-
Notifications
You must be signed in to change notification settings - Fork 56
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 still being maintained? #265
Comments
Hi @ikisler This tool is not being actively maintained no. I would highly recommend using |
Thanks for the quick response @jfmengels! I will check out |
Maybe put an |
@stil4m Would you be fine with me officially deprecating the tool? |
Hi Jeroen,
Yes. Do it :)
… On 2 Nov 2022, at 16:46, Jeroen Engels ***@***.***> wrote:
@stil4m <https://github.com/stil4m> Would you be fine with me officially deprecating the tool?
—
Reply to this email directly, view it on GitHub <#265 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFOFKFEHH5FXPN2DOIMKEDWGKEF5ANCNFSM6AAAAAAQ46DCJU>.
You are receiving this because you were mentioned.
|
@jfmengels If I'm honest, I don't see why it should be "deprecated". I understand the dependencies might be an issue. Either because of the installation step, or because of security issues. @ikisler @stil4m I forked the repo and updated all the npm dependencies. The tool works fine with just some minor tweaks. I also removed all the INFO logging ( it was too noisy for me ) and put it behind a flag. I'll use that from now on, but if you want I can make a PR here so you can update the original |
It should be deprecated because the project is not maintained anymore, and because a different solution — with better and more accurate reports and more powerful features — exists. Pretty much all of Elm Analyse's features exist in
Starting with a default configuration (like below) gives you the same thing, and more.
|
It just works ;) |
Hey there, is this library is still being maintained? The last release was ~3 years ago, and there are open security advisories (see #257).
Would there be any interest in bringing on another maintainer?
Alternatively, does anyone own a fork where they are maintaining security patches? I looked through the existing forks on GH but didn't see any that looked up to date.
Thank you!
The text was updated successfully, but these errors were encountered: