Repository navigation
Resolve dependency advisories while retaining Node 20 support - #21
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The lockfile contained the vulnerable versions reported by S5 and npm audit. Upgrade Vitest and refresh compatible transitive patches to remove every reported advisory while retaining the declared Node >=20 support.
Checked GitHub advisory ranges for the scanner's IDs: the selected versions are outside the affected ranges. This changes package.json and package-lock.json only; other direct dependency versions and the Node engine are retained.
Validation under Node 20.20.2:
npm ci, typecheck, lint, all unit tests and production build pass.npm audit --json: zero vulnerabilities.Closes #17. Independent of #20; combined validation confirms compatibility.