Repository navigation
chore: automated npm audit fix - #55
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 <noreply@anthropic.com>
|
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 |
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 run (2026-10-26).
What was fixed
npm audit fix(no--force) resolved 3 of the 10 reported vulnerabilities, all via non-breaking patch bumps inpackage-lock.json:shell-quote(direct dep)quote()nanoid(transitive, dev)source-map-js(transitive, dev)Only
package-lock.jsonchanged;package.jsonranges already covered the new versions.Not touched (needs manual review — major/breaking bumps)
These remain and were intentionally left alone since fixing them requires
--force(major version bumps), which this automation never applies:vitest2.1.9 → latest 5.0.5 (breaking) — pulls in fixes for@vitest/mocker(moderate),tinypool(critical),vite/vite-node/esbuild(moderate/high)zod3.25.76 → latest 4.6.7 (breaking) — GHSA-mrhx-c7xc-m3w5, high severity (memory exhaustion on oversized constrained collections)7 vulnerabilities (3 moderate, 2 high, 2 critical) remain, all gated behind these major upgrades.
Verification
npm run build(tsc) passed with no errors after the fix.npm testpassed: 195/195 tests across 8 files.Generated by Claude Code