Repository navigation
Conversation
…lnerabilities Lock file regenerated (cleared the next RCE/SSRF and dompurify XSS on its own). Direct upgrades: next ^16.3.8 Overrides: removed stale pins sharp, qs, nanoid, undici, js-yaml (postcss kept); the sharp pin was holding the vulnerable 0.35.4 in place. Vuln count: snyk 4 -> 0 (20 sharp-libvips license flags unchanged), npm audit 10 -> 5 (remaining are open-ended tooling ranges with no fix). Compiles; prerender needs real stack credentials, unchanged from main. Co-Authored-By: Claude Fable 5.1 <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 |
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
1 participant
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 flags
next16.3.4 (RCE innext/og, SSRF),dompurify3.4.15 (XSS) andsharp0.35.4 (use-after-free). The committed lock file is stale, and an earlier cleanup pinnedsharpto exactly 0.35.4 inoverrides, so the fixed 0.35.5 could never be picked up.Fix
package-lock.jsonfrom a clean install. That alone clears thenextanddompurifyfindings (nextlands on 16.4.0).nextfloor to^16.3.8so a fresh install can never land on the RCE versions.sharp(was blocking the fix), plusqs,nanoid,undici,js-yaml, which the tree already resolves past.postcsspin kept; it still holds a nested copy above 8.5.23.Result: Snyk real vulns 4 → 0 (the 20
sharplibvips license flags have no fix), npm audit 10 → 5. The remaining npm-audit rows (braces,fast-glob,micromatch,@next/eslint-plugin-next) are open-ended ranges with no fixed version and Snyk does not flag them.Verified:
next buildcompiles on the new lock file. Prerendering/needs real stack credentials, same as onmain.🤖 Generated with Claude Code