Repository navigation
chore: automated npm audit fix - #50
Closed
ProduktEntdecker wants to merge 1 commit into
Closed
ProduktEntdecker wants to merge 1 commit into
ProduktEntdecker wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Tg7K49RDQAwUD53nYWRMXS
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Comment |
This was referenced Oct 11, 2026
Owner
Author
|
Superseded by the new rolling PR #56, which carries the same fix (and will keep rolling forward each week instead of opening a new dated PR). Closing this one. Generated by Claude Code |
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.
Automated weekly dependency-hygiene check.
Fixed
3.3.16→3.3.19(dev dependency, via@vitest/mocker/vite-nodetransitive chain) — fixes GHSA-2v37-7h3g-55p8 (high severity: custom generators can loop indefinitely when size is zero).Applied via
npm audit fix(no--force, no major bumps). Onlypackage-lock.jsonchanged;package.jsonis untouched.Verified
npm ci— clean installnpm auditbefore: 6 vulnerabilities (3 moderate, 2 high, 1 critical) → after: 5 vulnerabilities (3 moderate, 1 high, 1 critical)npm run build(tsc) — passes with no errorsRemaining (needs manual review — NOT touched here)
5 vulnerabilities remain, all rooted in the
vitest/vite/esbuild/@vitest/mocker/vite-nodechain (dev-only test tooling):@vitest/mocker— moderate (path traversal / arbitrary file read, GHSA-82fw-gwwq-j7x9)esbuild— moderate (dev server request/response exposure, GHSA-67mh-4wv8-2f99)vite— high (transitive via vulnerable esbuild)vite-node— moderate (transitive via vulnerable vite)vitest— critical (transitive via all of the above)All require
npm audit fix --force, which would bumpvitestfrom2.1.9to5.0.3— a semver-major breaking change. Per policy this automated job never applies--forceor major version bumps. This needs a human-reviewedvitestv5 migration (test API/config changes) in a separate PR.Also outdated (informational, not touched)
No package version fields were changed, and no publish/version commands were run.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Tg7K49RDQAwUD53nYWRMXS
Generated by Claude Code