I recently found this project and found it very appealing, I decided to add it to my dev stack right away, however then I saw that last commit is from 2019-02-23 and there is an old pull request and several pretty old open issues. So I'm wondering if this has to do with the creator not having time to maintain this or if he decided it wasn't a good idea to keep working on. I think it is BTW.
So please @saadq , could you jump in and make a tiny commit to the README.md beginning so the community can know from a glimpse if this project is a no-go or you just got stacked up with work?
I offer my help to maintain this.
Currently I'm forking it to try to make security fixes on dependencies cause npm ci spits several security issues:
$ npm ci
...
added 330 packages, and audited 331 packages in 22s
34 vulnerabilities (14 moderate, 17 high, 3 critical)
I recently found this project and found it very appealing, I decided to add it to my dev stack right away, however then I saw that last commit is from 2019-02-23 and there is an old pull request and several pretty old open issues. So I'm wondering if this has to do with the creator not having time to maintain this or if he decided it wasn't a good idea to keep working on. I think it is BTW.
So please @saadq , could you jump in and make a tiny commit to the
README.mdbeginning so the community can know from a glimpse if this project is a no-go or you just got stacked up with work?I offer my help to maintain this.
Currently I'm forking it to try to make security fixes on dependencies cause
npm cispits several security issues: