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
When we start curating npm package vulnerabilities, we should also consider adding all known vulnerabilities in node itself. Right now they are mentioned in the release announcements/changelogs, but it would be valuable to have node itself listed in the DB, see #26
This would enable thirdparty tools to report not only any know vulns in the package dependencies, but also in the current (or any) version of node.
The text was updated successfully, but these errors were encountered:
When we start curating npm package vulnerabilities, we should also consider adding all known vulnerabilities in node itself. Right now they are mentioned in the release announcements/changelogs, but it would be valuable to have node itself listed in the DB, see #26
This would enable thirdparty tools to report not only any know vulns in the package dependencies, but also in the current (or any) version of node.
The text was updated successfully, but these errors were encountered: