It appears you've updated and finished 5.0.1 but have not published it to npm etc.
@kewde I note you released 5.0.1 16 days ago. Can this be published to npm so that we can pick up on these changes.
SNYK has identified an issue with 5.0.0 which is fixed by 5.0.1
Note that the repo readme reflects the changes in 5.0.1 not those that are in 5.0.0. Hence the discrepancy we are getting identifying sqlite3 as 3.31.1 (https://nvd.nist.gov/vuln/detail/CVE-2020-11656) and not 3.32.2 as declared in the readme.
Hugely appreciate your work on this.
Any progress on this?
We are wondering if there is any update on this
Hi, do you have an update on this? Is there anything we can do to help?
We can use the commit hash for now but there is no binary available (git://github.com/mapbox/node-sqlite3#e87dfa474dd89e20fd9361e7cf845aa88ae2ec1b)
@kewde adding to the rest of comments above :heavy_plus_sign: Would love to help 5.0.1 npm publish happen as well.
P.S. Big thanks for all the work you've put into this project :black_heart:
Same here 馃憤 (Posting here to be sure to get a notification)
Looks like this post might add some color:
https://kewde.github.io/sqlite
Sounds like kewde wants someone trustworthy with experience being a long-term open-source maintainer and who relies on node-sqlite3 for their business to step up and make a long-term commitment to helping maintain. Any takers?
5.0.1 has been published on npm :tada:
@awjreynolds think this issue can be closed now?
Fantastic!
thank you!
Most helpful comment
@kewde I note you released 5.0.1 16 days ago. Can this be published to npm so that we can pick up on these changes.
SNYK has identified an issue with 5.0.0 which is fixed by 5.0.1
Note that the repo readme reflects the changes in 5.0.1 not those that are in 5.0.0. Hence the discrepancy we are getting identifying sqlite3 as 3.31.1 (https://nvd.nist.gov/vuln/detail/CVE-2020-11656) and not 3.32.2 as declared in the readme.
Hugely appreciate your work on this.