Repository navigation
Conversation
…ndings Lock file regenerated (fixed 16 on its own). Direct upgrades: commitizen ^4.3.1 -> ^4.3.2 (devDependency). Overrides: none (published package with no runtime dependencies; the remaining fixes are cross-major). Vuln count: snyk 0 -> 0 (devDependencies only, nothing for snyk test to read), npm audit 21 -> 5. Build verified passing. Remaining (dev-only): jest-coverage-badges (mkdirp, minimist; no fixed release) and jest-junit 15 -> 17 major (uuid). Co-Authored-By: Claude Opus 5.5 <[email protected]>
✅ 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 |
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
npm audit reported 21 findings (4 critical, 8 high, 5 moderate, 4 low) in the committed lock file. They are all in development tooling: the published package has no runtime dependencies, so consumers were never exposed, but our CI and local installs were.
Fix
package-lock.jsonwithin the existing ranges, which clears 16 findings on its own (handlebars, lodash, form-data, ws, js-yaml, tmp, fast-uri, brace-expansion and others).commitizenfrom^4.3.1to^4.3.2so a fresh install cannot land on the affected 4.3.1.Still open (5, dev-only):
jest-coverage-badgespulls inmkdirp0.5.1 andminimist0.0.8 (3 critical), and every release from 1.1.2 up is affected, so there is nothing to upgrade to;jest-junit15 pulls inuuid8 (2 moderate) and needs the 17.x major.Verified: npm audit 21 → 5;
npm run buildpasses andnpm testpasses (430 tests).🤖 Generated with Claude Code