Skip to content

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

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

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

Conversation

@cs-raj

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

Copy link
Copy Markdown
Contributor

Problem

main has 2 open Snyk dependency findings (qs: SNYK-JS-QS-20943482, SNYK-JS-QS-21755395; npm audit 24). Repo is a LIBRARY (published @contentstack/types-generator).

Fix

Lock file regenerated; no package.json change was needed. Library note: consumers resolve our package.json ranges themselves, so this clears our own install/CI tree.

Verification

Snyk 2 → 0, npm audit 24 → 22. Build passes.

What remains

Only npm-audit findings with no same-range fix; Snyk Code (SAST) tickets are out of scope.


Generated by Claude Code

Lock file regenerated (fixed 2 on its own: SNYK-JS-QS-20943482, SNYK-JS-QS-21755395).
Vuln count: snyk 2 → 0, npm audit 24 → 22. Build verified passing.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XifDUYE5xMdSTy7Qnaj4zd
@cs-raj
cs-raj requested a review from a team as a code owner November 3, 2026 04:05
@snyk-io

snyk-io Bot commented Nov 3, 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

github-actions Bot commented Nov 3, 2026

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 0 25 ✅ Passed
🟡 Medium Severity 0 0 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

✅ 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.

3 participants