Skip to content

Commit 1e63362

Browse files
RafaelGSSmhdawson
andauthored
Update apps/site/pages/en/blog/vulnerability/upcoming-cve-for-eol-versions.md
Co-authored-by: Michael Dawson <mdawson@devrus.com> Signed-off-by: Rafael Gonzaga <rafael.nunu@hotmail.com>
1 parent 2042f36 commit 1e63362

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

apps/site/pages/en/blog/vulnerability/upcoming-cve-for-eol-versions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ For more details on this decision, you can refer to the discussion in
2525
## Why Issue a CVE?
2626

2727
Many organizations rely on CVE notifications to track security issues across
28-
their software stacks. The Node.js project guarantee a timely resolution and disclosure
28+
their software stacks. The Node.js project aims for a timely resolution and disclosure
2929
for all reported vulnerabilities for the _maintained_ release lines.
3030
However, we do not issue CVEs for EOL release lines.
3131
By issuing a CVE for EOL versions of Node.js, we aim to:

0 commit comments

Comments
 (0)