fix: resolve 8 security vulnerabilities via npm audit fix#239
Open
fix: resolve 8 security vulnerabilities via npm audit fix#239
Conversation
Fix critical/high/moderate CVEs in transitive dependencies: - handlebars (critical) - prototype pollution - vite (high) - path traversal, fs.deny bypass, arbitrary file read - lodash (high) - prototype pollution - flatted, picomatch, brace-expansion (high/moderate) - yaml (moderate) - stack overflow via deeply nested YAML All 252 tests pass after the fix.
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.
What
Runs
npm audit fixto resolve 8 security vulnerabilities found in transitive dependencies.Vulnerabilities Fixed
.maphandling (GHSA-4w7w-66w2-5vf9)server.fs.denybypass (GHSA-v2wj-q39q-566r)Why
Running
npm auditonmaincurrently reports 8 vulnerabilities (1 critical, 4 high, 3 moderate). These are all in the dev/build toolchain (vitest, vite, yaml) — no production runtime exposure — but they should still be resolved to keep the supply chain clean and pass security scanners.How
npm audit fixresolves the dependency tree to safe versions. The main change is pinning vitest to4.0.18(from4.1.5), which bundles a safe version of vite.Tested
npm audit→ 0 vulnerabilities ✅npm test→ 252 tests pass ✅