Repository navigation
chore: automated npm audit fix - #40
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 Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
Owner
Author
|
Überholt durch den neueren automatischen npm-audit-Lauf #50. Orchestrator-Aufräumen 11.10.2026, bei Bedarf wieder öffnen. |
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.
Summary
Automated weekly dependency hygiene sweep.
npm audit fix(no--force) applied.Fixed:
nanoid: 3.3.16 → 3.3.18 — fixes GHSA-2v37-7h3g-55p8 (high, custom generators can loop indefinitely when size is zero)Not auto-applied (would require breaking change, needs manual review):
vitest2.1.9 → 4.1.10 (major bump) would resolve the remaining chain:esbuild<=0.24.2 (moderate) — GHSA-67mh-4wv8-2f99vite<=6.4.2 (high) — GHSA-fx2h-pf6j-xcff and related moderate advisoriesvite-node<=2.2.0-beta.2 (moderate)@vitest/mocker<=3.0.0-beta.4 (moderate)vitest<=3.2.5 (critical) — GHSA-5xrq-8626-4rwpAll of these are dev-only dependencies (test tooling), not shipped in the published package. Bumping requires
npm audit fix --forceand was intentionally left out of this automated PR per policy — needs a human to review the vitest 2→4 migration separately.Also outdated (informational, not vulnerabilities):
@types/node: 22.19.3 → 22.20.1 (wanted) / 26.2.0 (latest, major)tsx: 4.21.0 → 4.23.12typescript: 5.8.3 → 7.0.2 (latest, major)zod: 3.25.76 → 4.4.3 (latest, major)Build & test status
npm run build(tsc): PASSEDnpm test(vitest, 195 tests across 8 files): PASSEDTest plan
npm auditno longer flagsnanoidGenerated by Claude Code