Skip to content

fix: regenerate lock file to resolve Snyk vulnerabilities - #89

Open
cs-raj wants to merge 1 commit into
mainfrom
fix/snyk-patch-deps-20261111
Open

cs-raj wants to merge 1 commit into
mainfrom
fix/snyk-patch-deps-20261111

Conversation

@cs-raj

@cs-raj cs-raj commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Problem

Snyk reports 8 distinct findings on main.

Fix

Regenerated the lock file (no package.json change, APP: the lock file is the deliverable). Clears 6 of 8 findings; 2 remain.

Still open after this PR:

  • http-cache-semantics@4.3.0: high (no fix)

These need a major bump or an upstream release; no safe patch/minor bump or same-major override clears them.

Verification

Snyk + npm audit rescanned on the regenerated lock. Build: compile and type-check pass; the build then stops at page-data collection because no Stack credentials exist in this environment, same as unmodified main.


Generated by Claude Code

Lock file regenerated; no package.json change was needed.
Direct upgrades: none
Overrides: none
Vuln count: snyk 8 → 2, npm audit 0 → 0. Build checked (see PR).
@cs-raj
cs-raj requested a review from a team as a code owner November 11, 2026 04:02
@snyk-io

snyk-io Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

✅ 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

Copy link
Copy Markdown

🔒 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 2 25 ✅ Passed
🟡 Medium Severity 0 46 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: 2
  • Medium without fixes: 46
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants