fix(deps): resolve 14 Snyk vulnerabilities via upgrades and overrides

[cs-raj]

Problem

Snyk reported 14 security vulnerabilities on main (2 critical, 7 high, 5 moderate), and npm audit reported 6 (3 high, 3 moderate). Every one was transitive.

The dominant source was a single package: undici@8.10.0, reached via isomorphic-dompurify > jsdom, accounted for 11 of the 14 findings including both criticals.

Two entries in the existing overrides block had also gone stale and were themselves pinning vulnerable versions:

• qs pinned at ^6.15.3 — inside the affected range >=6.14.2 <=6.15.3
• sharp pinned at 0.35.3 — inside the affected range <0.35.4 (heap overflow)

Fix

	before	after
Snyk security	14 (C:2 H:7 M:5)	0
npm audit	6 (high:3 moderate:3)	0

Direct dependency upgrades (patch/minor only, no majors):

• next ^16.2.12 → ^16.3.4
• react ^19.2.8 → ^19.3.0
• react-dom ^19.2.8 → ^19.3.0

Transitive fixes via overrides:

• undici → ^8.10.2 (new) — clears 11 findings incl. both criticals
• js-yaml → ^4.3.2 (new) — clears 1 high (CPU DoS, GHSA-2883-xcg3-v3hh, via @eslint/eslintrc)
• qs ^6.15.3 → ^6.16.0 — clears 2 moderate
• sharp 0.35.3 → 0.35.4 — clears 1 high

Version bumped 1.3.3 → 1.3.4.

Deliberately not taken: Snyk's suggested remedy for the undici cluster was a major bump of isomorphic-dompurify 3.23.0 → 4.0.0. Rejected in favour of a same-major undici override that fixes all 11 identical issues.

Build verification — please read

npm run build fails on this branch, and it fails identically on unmodified main. This was verified by checking out pristine HEAD into a separate directory and running npm ci against the original lockfile: byte-identical error, Error: API key for Stack is required at lib/contentstack.ts:8, followed by Failed to collect page data for /.

The cause is environmental, not a dependency regression: this SSG kickstart fetches Contentstack content at build time, so next build requires valid Stack credentials, which are not available in the environment this ran in. AGENTS.md in this repo states its CI "focuses on security and policy, not app build verification" — there is no build workflow, because it cannot run without a stack.

Everything a dependency upgrade could plausibly break did pass on the upgraded tree: TypeScript compiled successfully in 90s, and npm run lint passed clean. The failure occurs strictly after compilation, at the data-fetch step.

Please run npm run build with valid Contentstack credentials before merging.

Remaining findings (not addressable here)

• 10 LGPL-3.0 license notices (medium) on @img/sharp-libvips-*@1.3.2 via next > sharp. License metadata only; no non-LGPL alternative exists.
• isomorphic-dompurify stays ^3.23.0 (latest is 4.2.0, a major). No outstanding vulnerability, but 3.23.0 is deprecated upstream and raised its Node floor to ^22.22.2 without a major bump, so it emits EBADENGINE on Node 22.21.x.
• typescript stays ^5 (latest is 7.x, a major). Not vulnerable.
• snyk code test (SAST) returned findings for files that do not exist in this repo (src/main.ts, a knex service spec, a DB migration) — this repo contains only lib/ and pages/. This looks like a server-side project-mapping collision and was not actioned; treat that SAST output as unreliable for this repo.

🤖 Generated with Claude Code

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[github-actions]

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type	Count (with fixes)	Without fixes	Threshold	Result
🔴 Critical Severity	0	0	10	✅ Passed
🟠 High Severity	0	0	25	✅ Passed
🟡 Medium Severity	0	20	500	✅ Passed
🔵 Low Severity	0	0	1000	✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity	Breaches (with fixes)	Breaches (no fixes)	SLA Threshold (with/no fixes)	Status
🔴 Critical	0	0	15 / 30 days	✅ Passed
🟠 High	0	0	30 / 120 days	✅ Passed
🟡 Medium	0	0	90 / 365 days	✅ Passed
🔵 Low	0	0	180 / 365 days	✅ Passed

ℹ️ 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:

• Critical without fixes: 0
• High without fixes: 0
• Medium without fixes: 20
• Low without fixes: 0

✅ BUILD PASSED - All security checks passed

[amit-kanswal-cs]

LGTM