chore(frontend): bump vitest to 4.1.11 to clear the mocker path-traversal advisory - #60
Merged
Merged
Conversation
…rsal advisory GHSA-82fw-gwwq-j7x9 (path traversal / arbitrary file read via the @vitest/mocker redirect mock) covers >=2.1.0 <4.1.11, so the fix is a patch release rather than a major bump. vitest and @vitest/coverage-v8 pin each other at an exact version, which makes both 'npm audit fix' and 'npm update' no-ops here; the two have to move together via an explicit install. That also raises the declared floor above the vulnerable range instead of leaving the caret pointing at 4.1.10. npm audit now reports 0 vulnerabilities.
There was a problem hiding this comment.
🟢 Approval recommended
The advisory is addressed, and all supplied verification checks pass.
Pull request overview
Updates frontend Vitest dependencies to 4.1.11, addressing the mocker path-traversal advisory.
Changes:
- Bumps Vitest and coverage provider dependency floors.
- Refreshes patched Vitest and transitive lockfile entries.
File summaries
| File | Description |
|---|---|
frontend/package.json |
Raises Vitest dependency floors to 4.1.11. |
frontend/package-lock.json |
Locks patched Vitest packages and refreshed transitive dependencies. |
Review details
Files not reviewed (1)
- frontend/package-lock.json: Generated file
- Files reviewed: 1/2 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
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.
Clears the three moderate advisories
npm auditwas reporting infrontend/. All three (vitest,@vitest/coverage-v8,@vitest/mocker) trace back to a single advisory: GHSA-82fw-gwwq-j7x9, path traversal / arbitrary file read via the@vitest/mockerredirect mock.The advisory range is
>=2.1.0 <4.1.11, so this is a patch bump — no vitest 5 migration needed.Why the manifest changed too
vitestand@vitest/coverage-v8pin each other at an exact version ("vitest": "4.1.10"as a peer of coverage-v8, and vice versa). That circular exact pin makes bothnpm audit fixandnpm updateno-ops — verified, both left the tree at 4.1.10. The two have to move together via an explicit install, which also raises the declared floor above the vulnerable range rather than leaving the caret pointed at^4.1.10.Beyond the vitest packages, four of vitest's own transitive deps floated within their existing caret ranges:
es-module-lexer,obug,tinyexec,tinyrainbow.Verification
All run from
frontend/against the new lockfile:npm ci— cleannpm audit --package-lock-only— found 0 vulnerabilitiesnpm run test:ci— exit 0; 31 test files, 165 tests, all passed (covers both the runner and the v8 coverage provider that were bumped)npm run build— exit 0, bundle still self-contained and CSP hash-pinnednpm run typecheck— exit 0npm run lint— exit 0 (13 pre-existing warnings, 0 errors)Note this was never gating CI: the
security-auditjob runsnpm audit --audit-level=high, and these were moderates. This is cleanup.