Repository navigation
fix(deps): resolve Snyk and npm audit vulnerabilities - #73
Conversation
Upgrade direct dependencies to the latest patch/minor releases and add overrides for transitive packages that cannot be fixed by a direct bump. Direct dependencies: - next 16.2.12 -> 16.3.4 - react / react-dom 19.2.8 -> 19.3.0 - eslint-config-next 16.2.12 -> 16.3.4 Overrides: - qs ^6.15.3 -> ^6.16.0 (resource exhaustion, uncaught exception) - sharp 0.35.3 -> 0.35.4 (heap-based buffer overflow via libheif) - undici ^8.10.2 (new; 2 critical, 5 high, 4 medium via jsdom) - js-yaml ^4.3.2 (new; CPU exhaustion via empty merge sources) Snyk security issues drop from 14 (2 critical, 7 high, 5 medium) to 0 and npm audit from 6 (3 high, 3 moderate) to 0. Remaining Snyk findings are LGPL-3.0 license notices on optional @img/sharp-libvips binaries. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
…y-resolution Conflicts resolved to the newer value per line: next ^16.4.1 and sharp 0.35.5 from main; react/react-dom ^19.3.0 and qs ^6.16.0 from the PR; PR's undici ^8.10.2 and js-yaml ^4.3.2 overrides kept. package-lock.json taken from the PR side (regenerated next). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…k vulnerabilities Lock file regenerated (fixed 8 of 11 vs main on its own: undici 8.12.1 -> 8.12.3). Direct upgrades: none Overrides: dompurify 3.4.16 -> 3.4.17 (existing pin raised) Vuln count: snyk 11 → 0, npm audit 2 → 0. Build verified passing. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
46050d1
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
Problem
Snyk reports 11 vulnerabilities on
main(3 critical, 7 high, 1 low):undici8.12.1 (8, viaisomorphic-dompurify > jsdom) anddompurify3.4.16 (3, pinned inoverrides). npm audit reports 2. This branch also predated #75 and conflicted withmain.Fix
APP (Next.js, built with
next build), so the lock file is the deliverable. No package version bump (already 1.2.4).maininto this branch, keeping the newer value on each conflicting line:next^16.4.1 andsharp0.35.5 frommain;react/react-dom^19.3.0 andqs^6.16.0 from this PR; this PR'sundici^8.10.2 andjs-yaml^4.3.2 overrides kept.package-lock.json:undici8.12.1 -> 8.12.3 clears 8 findings on its own.dompurifyoverride 3.4.16 -> 3.4.17 (the pin held the 3 open XSS findings).Remaining:
@img/sharp-libvips-*, MPL-2.0lightningcss-linux-x64-gnu): not fixable by a version bump.Verified:
npm run buildpasses (Next.js 16.4.3). Snyk 11 -> 0, npm audit 2 -> 0.🤖 Generated with Claude Code