fix: upgrade vulnerable direct dependencies#2820
Open
sonukapoor wants to merge 1 commit into
Open
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.
This upgrades four direct dependencies to their first safe versions, based on findings from the CVE Lite dependency audit introduced in PR #2819.
A scan of the current pnpm lockfile found 34 vulnerabilities - 3 critical, 16 high, 14 medium, 1 low. Four of those are direct dependencies with confirmed safe versions and copy-run fix commands.
vitest upgraded from 2.1.9 to 4.0.0 - critical severity, CVE in the 2.x series.
rollup in packages/solid-ssr upgraded from 4.56.0 to 4.59.0 - high severity finding in the 4.56.x range.
turbo upgraded from 1.13.4 to 2.9.14 - medium severity, addressing a known issue in the 1.x line.
@babel/core in packages/babel-preset-solid and packages/solid-ssr upgraded from 7.28.6 to 7.29.6 - low severity advisory.
All changes were applied via pnpm and the lockfile is updated accordingly. The remaining 30 findings are transitive - they cannot be fixed by upgrading solid's own direct deps and would require upstream changes in the affected dependency chains.