Repository navigation
fix(dashboard): update vite to clear the launch-editor audit advisories - #119
Merged
Merged
Conversation
vite 6.4.3 -> 6.4.4 (lockfile only; package.json range ^6.0.0 unchanged). Clears the three launch-editor advisories that failed 'npm audit --audit-level=high'. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Oct 21, 2026
Merged
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
1 participant
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.
What failed: CI job "Dashboard build + audit" is red on master.
npm audit --audit-level=highflagsvite <=6.4.3for three launch-editor advisories (GHSA-698v-4r3x-3vcv, GHSA-r825-w8mm-5pxw, GHSA-587h-7wmj-h5pm).Why it only affects the dev toolchain: vite is a devDependency. It runs only in the dev server and the build. It is not part of the dashboard bundle that ships in the zip.
What changed: vite 6.4.3 -> 6.4.4 in
package-lock.json(3 lines). package.json is unchanged and stays on the 6.x line. It was done withnpm audit fix(no --force).How verified: from a clean
npm ci,npm audit --audit-level=highexits 0 and the fullnpm auditreports 0 vulnerabilities. The build passes, all 69 tests pass, and the built output is byte-identical in size (325,201 bytes, same asset hashes).🤖 Generated with Claude Code