You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 1, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 1, 2026. It is now read-only.
@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.
Reacted by Vladimir Voronkov, Themistoklis Chatziemmanouil, MigFerreira, Steven Roussey, Jurriaan Barkey Wolf, Alvis Tang, Mark Wylde, Ostap Chervak, F7502, Daniel Lockyer and 9 more
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)
Reacted by Alex Recuenco, Mark Wylde, Jarrod Connolly, naz and Joël Galeran
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?
Activity
awjreynolds commentedon Sep 25, 2020
@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.
ducqhl commentedon Oct 28, 2020
Any progress on this?
alexrecuenco commentedon Nov 5, 2020
We are wondering if there is any update on this
hverlin commentedon Nov 20, 2020
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)
Fixed sqlite3 errors when email analytics jobs run
Fixed sqlite3 errors when email analytics jobs run (#12431)
naz commentedon Nov 29, 2020
@kewde adding to the rest of comments above ➕ 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 🖤
Jolg42 commentedon Dec 2, 2020
Same here 👍 (Posting here to be sure to get a notification)
trevyn commentedon Dec 18, 2020
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?
naz commentedon Jan 11, 2021
5.0.1 has been published on npm 🎉
naz commentedon Jan 11, 2021
@awjreynolds think this issue can be closed now?
awjreynolds commentedon Jan 11, 2021
Fantastic!
ducqhl commentedon Jan 14, 2021
thank you!
Added protective code to update-check job