fix(frontend): resolve npm audit advisories keeping Security Scanning red - #1345
Conversation
Bump four dev-tooling deps to clear all high/critical advisories caught by
`npm audit --audit-level=high` in the Security Scanning CI job:
- @typescript-eslint/{eslint-plugin,parser} ^6 -> ^8 (fixes GHSA-3ppc-4f35-3m26,
GHSA-7r86-cg39-jmmj, GHSA-23c5-xmqv-rm74 via minimatch in typescript-estree)
- copy-webpack-plugin ^13 -> ^14 (fixes GHSA-5c6j-r48x-rmvq, GHSA-qj8w-gfj5-8c6v
via serialize-javascript)
- css-minimizer-webpack-plugin ^5 -> ^8 (same serialize-javascript chain)
All four are dev-only build/lint tooling with low blast radius. Verified:
- npm audit --audit-level=high: 0 vulnerabilities (exit 0)
- npm run typecheck: exit 0
- npm run build: exit 0
- npm test: 77 suites, 2553 passed, 1 skipped (exit 0)
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 1 minute Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
@typescript-eslint/{eslint-plugin,parser}from^6.0.0to^8.0.0-- fixes GHSA-3ppc-4f35-3m26 / GHSA-7r86-cg39-jmmj / GHSA-23c5-xmqv-rm74 (ReDoS via minimatch in@typescript-eslint/typescript-estree)copy-webpack-pluginfrom^13.0.1to^14.0.0-- fixes GHSA-5c6j-r48x-rmvq / GHSA-qj8w-gfj5-8c6v (RCE + DoS inserialize-javascript)css-minimizer-webpack-pluginfrom^5.0.0to^8.0.0-- sameserialize-javascriptchainAll four are dev-only build/lint tooling. No
--omitflags or audit-level loosening were added to CI. No config changes required: the webpack config usesCssMinimizerPlugin()with zero options (drop-in upgrade), and there is no ESLint config file in the frontend directory so the@typescript-eslintv6->v8 jump needs no rule changes.Per-advisory notes
npm audit fix(semver-compatible updates)Verification
Closes #1344