-
Notifications
You must be signed in to change notification settings - Fork 6.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
blog: add Upcoming CVE for EOL Versions post #7328
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Please, do not land it until the TSC team reviews that. |
Should we mention the OpenJS Ecosystem Sustainability Program for the End-of-Life releases? |
* **Encourage Upgrades:** Prompt organizations and developers to update to | ||
actively supported Node.js versions. | ||
* **Improve Security:** Reduce the number of applications running outdated and | ||
unsupported versions of Node.js. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would cite/mention that most developers/companies would not update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add an example like:
Node.js v16, despite being EOL for over a year, has still 11 million downloads per month.
Refs: nodejs/security-wg#1401
cc: @nodejs/tsc @nodejs/security-wg @nodejs/security