Skip to content

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

Open
cs-raj wants to merge 1 commit into
masterfrom
fix/snyk-patch-deps-20261014
Open

cs-raj wants to merge 1 commit into
masterfrom
fix/snyk-patch-deps-20261014

Conversation

@cs-raj

@cs-raj cs-raj commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Problem

Snyk reports 2 medium findings in qs 6.15.3 (a transitive dependency of body-parser): SNYK-JS-QS-19432017 and SNYK-JS-QS-19432019. The committed lock file pins the vulnerable version.

Fix

Regenerated package-lock.json, which resolves qs to a fixed version (6.16.0 or later). No dependency range changes were needed and no overrides were added; the package version is bumped to 1.1.5.

This is a LIBRARY, so consumers resolve our package.json ranges themselves and body-parser already permits the fixed qs.

Remaining: 33 npm audit findings, all in dev tooling (jest 29 and its dependency tree, plus a few older transitive packages). They need a jest major upgrade (npm audit fix --force), which is out of scope for this patch.

Verified: Snyk 2 → 0, npm audit 33 → 33, npm run build-ts passes.

🤖 Generated with Claude Code

Lock file regenerated (fixed 2 on its own).
Direct upgrades: none
Overrides: none
Vuln count: snyk 2 → 0, npm audit 33 → 33. Build verified passing.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings October 14, 2026 08:42
@cs-raj
cs-raj requested a review from a team as a code owner October 14, 2026 08:42
@snyk-io

snyk-io Bot commented Oct 14, 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 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

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The lockfile resolves the reported vulnerable dependency to the fixed version, and package versions match.

0 open findings

What changed in this PR

This patch updates the library’s lockfile to resolve the reported qs vulnerabilities and bumps the package version to 1.1.5.

Changes:

  • Resolves qs to 6.16.0 without changing dependency ranges.
  • Refreshes other transitive lockfile entries and synchronizes the package version.
File Description
package.json Bumps the library version to 1.1.5.
package-lock.json Updates the version metadata and locked dependencies, including qs.

🧠 Review effort: Lite


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

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