deps: dashboard dependency sweep — npm audit (vite 8.1.0, js-yaml ≥4.2.0) + @vitejs/plugin-react 6.0.2 - #406
Conversation
Resolves 1 high + 2 moderate advisories surfaced after the Renovate lock-file maintenance: - vite 8.0.11 -> 8.1.0 (high): GHSA-fx2h-pf6j-xcff (server.fs.deny bypass) and GHSA-v6wh-96g9-6wx3 (launch-editor NTLMv2 hash disclosure). Minor bump within the 8.x major; both CVEs are Windows dev-server only. - js-yaml override ^4.2.0 (2x moderate): GHSA-h67p-54hq-rp68 quadratic-DoS in <=4.1.1, pulled in transitively by @redocly/openapi-core (via openapi-typescript) and cosmiconfig (via shadcn) — both dev-only tools. 4.2.0 is a backward-compatible minor; staying in 4.x avoids the ESM-only 5.x break for those CJS consumers. Verified: npm audit clean, vite build, vitest 18/18, eslint, tsc, and generate:ts produces identical src/types/api.ts. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
|
🚅 Deployed to the qyl-pr-406 environment in qyl
|
Resolve dashboard dependency conflicts: keep main's newer pins (typescript-eslint 8.62.0, vitest 4.1.9, and the other landed bumps), keep this PR's audit fixes (vite 8.1.0 > main's 8.0.16, js-yaml ^4.2.0 override forcing js-yaml 4.1.1 -> 4.2.0). Lockfile regenerated to match. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
plugin-react 6.0.2 makes npm try to install its OPTIONAL @rolldown/plugin-babel peer, whose @babel/plugin-transform-runtime@8 -> @babel/core@^8 chain conflicts with the project's @babel/core@7 (required by plugin-react's own babel-7 path), causing an ERESOLVE. The dashboard does not use rolldown's babel transform, so pin the optional tooling to babel 7 via an override; npm then skips the babel-8 chain and resolves cleanly. Verified locally: npm ci, build, and 18/18 tests pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Folded in @vitejs/plugin-react 6.0.2 (was the separate #401, now superseded). 6.0.2 made npm try to install its optional |
Clears the 1 high + 2 moderate
npm auditadvisories the dashboard surfaced after the recent Renovate lock-file maintenance.Changes
server.fs.denybypass on Windows alternate paths) + GHSA-v6wh-96g9-6wx3 (launch-editor NTLMv2 hash disclosure via UNC paths). Minor bump within the 8.x major; both CVEs are Windows dev-server only.overrides: { "js-yaml": "^4.2.0" }(2× moderate) — GHSA-h67p-54hq-rp68 quadratic-complexity DoS in js-yaml<=4.1.1, pulled in transitively by dev-only tooling:@redocly/openapi-core(viaopenapi-typescript) andcosmiconfig(viashadcn).npm audit fixcouldn't apply it because those parents pin/resolve4.1.1;4.2.0is a backward-compatible minor and staying in 4.x avoids the ESM-only 5.x break for those CJS consumers.Verification
npm audit→ 0 vulnerabilities (was 1 high + 2 moderate)vite build✓ ·vitest18/18 ✓ · ESLint (src) +tsc -bcleannpm run generate:tsregenerates an identicalsrc/types/api.ts— dev tooling intact on js-yaml 4.2.0🤖 Generated with Claude Code