Repository navigation
Conversation
Overrides added: @hono/node-server: 2.0.6 → 2.0.10 (fixes moderate DoS via aborted WebSocket handshake) less: 4.4.2 → 4.7.0 (fixes high infinite-loop vulnerability) Package version: 0.1.3 → 0.1.4 Vuln count: 6 (before) → 0 (after). Build verified passing. Skipped (no safe fix available): image-size: vulnerable range is *, no safe version to pin @modelcontextprotocol/sdk: proposed fix is a cross-major downgrade (1.x → 0.x) Co-Authored-By: Claude Sonnet 4.6 <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 |
…0260811 # Conflicts: # package-lock.json
Lock file regenerated (fixed 0 Snyk and 3 npm audit findings on its own). Direct upgrades: @angular-devkit/build-angular 21.2.28, @angular/cli 21.2.28, vite ^6.4.5 Overrides: qs 6.16.1 .talismanrc: package-lock.json entry ignores filecontent + base64content. Vuln count: snyk 1 → 0, npm audit 12 → 5. Build verified passing. Co-Authored-By: Claude Opus 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 |
Problem
Snyk flags
qs6.16.0 onmain(high, Uncaught Exception, SNYK-JS-QS-20943482). It comes in through@contentstack/delivery-sdk→@contentstack/core, which pinsqsto exactly 6.16.0. npm audit reports 12 findings in the Angular build tooling, and this PR had fallen behindmain.Fix
This is a demo app, so the lock file is what ships. All changes are in
package.jsonand the lock file.mainand regeneratedpackage-lock.json.@angular-devkit/build-angular21.2.20 → 21.2.28,@angular/cli21.2.26 → 21.2.28 andvite^6.4.3 → ^6.4.5 (all patch releases).qs6.16.1 override. Kept this PR's earlier@hono/node-server2.0.10 andless4.7.0 overrides and version 0.1.4..talismanrcso Talisman also skips base64content inpackage-lock.json(the lock's integrity hashes).npm cion npm 10 installs it.What remains: 5 npm audit findings, all in build tooling and all caused by
piscina5.2.0 andundici7.29.0. The existing overrides onmainpin them to those versions. The fixes (5.3.2 and 7.30.1) are on the same major, but this PR does not change them. The 2 MPL-2.0 licence findings (lightningcss) need a policy decision, not a version bump.Verified:
npm run buildpasses. Snyk 1 → 0, npm audit 12 → 5.🤖 Generated with Claude Code