🛡️ Sentinel: Improve EOL detection for odd and legacy versions #807
+38
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🛡️ Sentinel: [Security Enhancement] Improve EOL detection
Vulnerability:
The library previously only checked EOL status against a hardcoded list of recent LTS versions (18, 20, 22, 24). This meant that running on:
isEOL: false.isEOL: false(if not in the map).This could mislead users or tools relying on this library into thinking they are running on a supported, secure Node.js version when they are not.
Fix:
EOL_DATESto include versions 12, 14, 16, 17, 19, 21, 23.checkEOLlogic to explicitly mark any major version < 12 as EOL.Verification:
bun run testpasses.isEOL: true.PR created automatically by Jules for task 10994980416293653299 started by @srod
Summary by cubic
Improves Node EOL detection to correctly flag odd majors and legacy versions as unsupported, ensuring accurate security warnings. Adds missing EOL dates and a safe fallback for very old versions.
Written for commit 6dbcaf1. Summary will update on new commits.