Node Version Audit – Audit Your Node Version for Known CVEs and Patches
Node Version Audit – Audit Your Node Version for Known CVEs and Patches
I wrote Node Version Audit to automatically keep track of Node patches, particularly for releases that fix CVEs. While it can be ran directly, it is designed to run as part of a pipeline to produce warnings if the runtime version of Node has CVEs, or is no longer supported. The cool part (IMO), is that Node Version Audit automatically keeps track of node releases and CVEs by parsing the change log, and so there is no curation needed to maintain it. I would love any thoughts!
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
Distributed version of the Mona Lisa evolution with migrations (Node)
Nuño's Stupid Node Version Manager
nodenv - Node version management, based on rbenv
NBLAS, Node C++ bindings to CBLAS
Scaffold out a modest node module
node-scrunch
MongoSync for Backbone/Node
Node Knockout 2013 entries
node-mongoose-fixtures
Assert.env: one fell swoop loading and asserting settings in node