Repository navigation
fix: regenerate lock file to resolve Snyk vulnerabilities - #97
Merged
Merged
Conversation
Lock file regenerated (fixed 9 on its own). Direct upgrades: none Overrides: none Vuln count: snyk 9 → 0, npm audit 2 → 0. No build script; require() smoke check of every direct dependency passes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
amit-kanswal-cs
approved these changes
Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The committed lock file pinned two vulnerable transitive packages: undici 7.30.0 (2 critical, 6 high Snyk findings) and body-parser 2.3.0 (1 high). npm audit reported 2 high findings.
Fix
package-lock.jsononly; nopackage.jsonchange. undici moves to 7.30.1 and body-parser to 2.4.0, both inside the ranges our dependencies already allow (on-finished and @mongodb-js/saslprep also take patch updates).Remaining
Nothing flagged. eslint 8 and rimraf 4 have newer majors, left alone since they fix nothing here.
Verification
Snyk 9 -> 0, npm audit 2 -> 0. The repo has no build script; every direct dependency loads with
require()on Node 22.🤖 Generated with Claude Code