[cs-raj]

Summary

Clean lock file regeneration plus dependency bumps for kickstart-sveltekit, with a patch version bump, raised directly against main as requested. It carries the same hand edits as #64 (still open against development), rebuilt on top of the current main.

Version bump

Branch	package.json version
main	0.1.3
development	0.1.2 (behind main)
this PR	0.1.4 (patch bump over main)

The 0.1.4 bump is the version edit already made by hand in the working tree; it is above main.

What changed

• package.json: version 0.1.3 -> 0.1.4 and 15 range changes across dependencies, devDependencies, optionalDependencies and overrides (for example @contentstack/delivery-sdk ^5.5.2 -> ^5.6.2, @contentstack/live-preview-utils ^4.4.5 -> ^4.5.3, eslint-plugin-svelte ^3.22.0 -> ^3.23.1, globals ^17.9.0 -> ^17.14.0, prettier ^3.9.6 -> ^3.9.10, svelte ^5.56.8 -> ^5.57.3, svelte-check ^4.7.5 -> ^4.7.8, typescript-eslint ^8.61.1 -> ^8.72.1). These dependency edits were made by hand in the working tree before this run and are included as they were.
• package-lock.json: deleted together with node_modules, then regenerated with a clean npm install (lockfileVersion 3).

Snyk (snyk test, vulnerabilities only; licence findings listed separately)

Scan	Critical	High	Medium	Low	Total
Before: committed lock on main	0	0	0	0	0
Lock regen only (committed package.json, fresh lock)	0	0	0	0	0
After: this PR (bumps + fresh lock)	0	0	0	0	0

Fixed by the lock regeneration alone: none.

Fixed additionally by the package.json bumps: none.

Remaining vulnerabilities: none.

New vulnerabilities introduced: none.

Licence findings: 2 after (lightningcss-linux-x64-gnu MPL-2.0, lightningcss-linux-x64-musl MPL-2.0), 2 before.

Build and checks

Script	This PR	main as committed
npm run build	passes	not run (passes on this PR)
npm run lint	fails (exit 1)	fails (exit 1)
npm run check	passes	not run (passes on this PR)

There is no test script in this repo.
Run on Node v22.23.3 with the placeholder values from .env.example as environment; npm install exit code 0. A failure that is identical on main as committed is not caused by this change.

Notes

• package.json differs from fix: regenerate lock file and bump deps to resolve Snyk vulnerabilities (0.1.4) #64 only by two overrides that exist on main but not on development (cookie 0.7.1 and qs ^6.16.2); they are kept so nothing already on main is dropped.
• main already had the earlier Snyk fixes (fix: bump 17 deps and add 2 overrides to resolve Snyk vulnerabilities #55, fix: regenerate lock file to resolve Snyk vulnerabilities #62), so the committed lock on main scans clean (0 vulnerabilities) before this PR; the regeneration keeps it at 0.
• npm run lint is prettier --check .; it fails on main as committed and fails the same way here.
• Nothing was merged and nothing was pushed to main directly.

🤖 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	2	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: 2
• Low without fixes: 0

✅ BUILD PASSED - All security checks passed