Repository navigation
fix(deps): update Vitest mocker security - #492
Open
alvaroloes wants to merge 1 commit into
Open
alvaroloes wants to merge 1 commit into
alvaroloes wants to merge 1 commit into
Conversation
alvaroloes
marked this pull request as ready for review
October 22, 2026 17:30
This branch has not been deployed
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.
Closes #489.
Problem
Vitest 4.1.11 pulls
@vitest/mockerversions affected by the manual mock code-injection and Windows backslash redirect-traversal advisories. This also makes the repository's all-severity dependency audit fail.Change
Validation
node --test --test-concurrency=1 scripts/vitest-security.test.mjs— 2 passed;pnpm audit --audit-level low— passes with only the repository's three existing reviewed exceptions.The full repository and Docker checks run in CI on this exact branch.