Repository navigation
chore: automated npm audit fix - #41
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 run.
npm audit fix(no--force) was applied.Fixed (non-breaking):
nanoid3.3.16 → 3.3.18 — resolves:Not auto-fixed (would require a semver-major bump, so left untouched per policy — no
--forceused):vitest(dev dependency) and its transitive chain (vite,vite-node,@vitest/mocker,esbuild) — fix requiresvitest@4.1.10, a breaking major upgrade from the current^2.0.0range. Covers 1 critical, 1 high, 3 moderate advisories, most notably GHSA-5xrq-8626-4rwp (critical: arbitrary file read/execute when Vitest UI server is listening).These require a manual, deliberate major-version upgrade and are reported separately below for visibility — not part of this PR.
Outdated (not touched — informational only)
@types/nodetsxtypescriptvitestzodTest plan
npm ci— clean install succeedednpm audit fix(no--force) applied — only touchedpackage-lock.json(nanoidbump)npm run build(tsc) — passed after the fix🤖 Generated by an automated weekly dependency-hygiene routine.
Generated by Claude Code