Skip to content

fix: resolve Snyk vulnerabilities (regenerate lock file, bump patch) - #94

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

npm audit on the committed lock file reports 42 findings (1 critical, 33 high, 7 moderate, 1 low); Snyk reports 0. Most of the transitive ones were pinned by stale resolutions in package-lock.json.

Fix

Library: consumers resolve our package.json ranges, not our lock file, so this mainly clears our own dev/CI install.

  • Regenerated package-lock.json: npm audit 42 → 38 (critical 1 → 0, high 33 → 29, low 1 → 0).
  • No direct bump clears a finding without a major; no override is safe (all cross-major or open-ended ranges). Package version 1.0.15 → 1.0.16.
  • Remaining 38 (jest/ts-jest/@types/jest/node-notifier/tslint toolchain, all dev-only) need major bumps: jest 30, ts-jest, tslint replacement.

Verified: npm run build-ts passes.

🤖 Generated with Claude Code

Lock file regenerated (npm audit 42 -> 38 on its own).
Direct upgrades: none (remaining findings need major bumps)
Overrides: none
Vuln count: snyk 0 -> 0, npm audit 42 -> 38. Build verified passing.
Package version 1.0.15 -> 1.0.16.

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 the build passes.

0 open findings

What changed in this PR

Updates the package patch version and regenerates the npm lockfile to refresh vulnerable transitive dependencies.

Changes:

  • Bumps version from 1.0.15 to 1.0.16.
  • Refreshes dependency resolutions and integrity metadata.
File Description
package.json Updates the package version.
package-lock.json Refreshes locked dependencies 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