Skip to content

fix: regenerate lock file to resolve npm audit vulnerabilities - #112

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

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

The committed lock file pins vulnerable transitive versions: npm audit reports 42 findings on master (1 critical, 33 high). Snyk reports 0 on the production tree. This is a LIBRARY, so consumers resolve our package.json ranges themselves and this lock file only affects our own dev/CI install.

Fix

  • Regenerated package-lock.json (fixes 5 npm audit findings with no manifest change, including the critical).
  • No direct bump or override added: none of the patch/minor bumps clears a finding, and the remaining findings need majors.
  • Package version 1.5.3 -> 1.5.4.
  • Remaining npm audit findings (37, all dev-only via jest, ts-jest, @types/jest, node-notifier) need major bumps (jest 30, node-notifier 11), left for a separate change.

Verified: npm run build-ts passes; Snyk 0 -> 0, npm audit 42 -> 37.

🤖 Generated with Claude Code

Lock file regenerated (fixed 5 of 42 npm audit findings on its own).
Direct upgrades: none (no patch/minor bump clears a finding)
Overrides: none
Version: 1.5.3 -> 1.5.4
Vuln count: snyk 0 -> 0, npm audit 42 -> 37. 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
@cs-raj cs-raj self-assigned this Oct 14, 2026
@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 reviewed changes are complete and reduce audit findings without altering dependency ranges.

0 open findings

What changed in this PR

Regenerates the npm lockfile to reduce audit findings and bumps the package version to 1.5.4.

Changes:

  • Refreshes transitive dependency resolutions and lockfile metadata.
  • Updates the package version from 1.5.3 to 1.5.4.
  • Retains remaining dev-only findings for a future major upgrade.
File Description
package.json Bumps the package version.
package-lock.json Refreshes locked dependency versions and metadata.

🧠 Review effort: Lite


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

@cs-raj

cs-raj commented Oct 14, 2026

Copy link
Copy Markdown
Contributor Author

Closing: this only regenerated the lock file and bumped the version, and no Snyk finding changes (0 before, 0 after). Not needed.

@cs-raj cs-raj closed this Oct 14, 2026
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