Repository navigation
fix: bump next, delivery-sdk and raise qs, sharp overrides to resolve Snyk vulnerabilities - #82
Merged
Merged
Conversation
… Snyk vulnerabilities Lock file regenerated (fixed 22 on its own). Direct upgrades: next ^16.4.1, @contentstack/delivery-sdk ^5.6.1 Overrides: qs 6.16.0, sharp 0.35.5 Vuln count: snyk 26 -> 1, npm audit 15 -> 5. Build verified passing. Co-Authored-By: Claude Sonnet 5.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 |
amit-kanswal-cs
approved these changes
Oct 15, 2026
reeshika-h
approved these changes
Oct 15, 2026
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.
Problem
Snyk reports 26 vulnerable dependency findings (2 critical, 9 high) on
main: undici, next, dompurify, qs and sharp. This repo is an APP (Next.js), so the lock file is what ships.Fix
package-lock.json(clears 22 findings on its own, mostly undici and dompurify).next^16.2.12 -> ^16.4.1 and@contentstack/delivery-sdk^5.6.0 -> ^5.6.1; package version 1.2.2 -> 1.2.3.qsoverride 6.15.3 -> 6.16.0 and the existingsharpoverride 0.35.3 -> 0.35.5 (same major, in the shipped tree).Remaining
qsfinding: Snyk now lists 6.16.1 as the fix, published after the 6.16.0 pin.@img/sharp-libvips-*,lightningcss-linux-x64-gnu), which a version bump does not fix.eslint-config-nextnpm audit chain that only a major bump fixes.Verification
Snyk 26 -> 1, npm audit 15 -> 5; build passes.
🤖 Generated with Claude Code