Skip to content

chore(deps): run npm audit fix to upgrade deps - #84

Merged
markmybytes merged 1 commit into
mainfrom
chore/npm-audit-fix
Nov 16, 2026
Merged

markmybytes merged 1 commit into
mainfrom
chore/npm-audit-fix

Conversation

@markmybytes

@markmybytes markmybytes commented Nov 15, 2026 •

Copy link
Copy Markdown
Owner

Summary

  • Run npm audit fix on frontend/: 69 → 11 vulnerabilities (was 1 low / 52 moderate / 15 high / 1 critical, now 1 low / 10 moderate)
  • Notable fixed advisories: @vue/server-renderer XSS (high), vitest/@vitest/mocker path traversal + code injection, vite server.fs.deny bypass, esbuild Windows file read
  • Bumps: vue → 3.5.42, vite → 8.3.8, vitest/@vitest/coverage-v8 → 4.1.11, plus ~160 transitive updates in the lockfile
  • vue 3.5.42 tightened defineModel typings — array defaults must now be factory functions; adapted DriverSelector.vue and TaggedInput.vue

- bump vue 3.5.42, @vue/server-renderer (high XSS), vite 8.3.8/esbuild,
  vitest 4.1.11 + @vitest/coverage-v8 (path traversal, code injection)
- adapt defineModel array defaults to factory functions required by
  vue 3.5.42 typings (DriverSelector, TaggedInput)
- remaining 11 advisories are all the typescript-eslint@8.72.2 ->
  minimatch chain; 8.72.2 is the latest published, waiting on upstream
@markmybytes markmybytes changed the title chore(deps): npm audit fix — 69 to 11 vulnerabilities chore(deps): run npm audit fix to upgrade deps Nov 16, 2026
@markmybytes
markmybytes merged commit b291e07 into main Nov 16, 2026
2 checks passed
@markmybytes
markmybytes deleted the chore/npm-audit-fix branch November 16, 2026 11:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant